Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8961c36467531ddad478554b6573681bc5fdf948b4ecf118f8576f8088f4db58

Tx prefix hash: 960a3afb07d6becb8fb742dd7c4fb055c3ca9bf60dbae7645cfa27172ab86d7d
Tx public key: bf18f92f078308d3ce56c44c1d7226dab116f6a3c0c6b6d8d90c465bc814ff02
Timestamp: 1706538204 Timestamp [UCT]: 2024-01-29 14:23:24 Age [y:d:h:m:s]: 01:284:15:27:45
Block: 945925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462240 RingCT/type: yes/0
Extra: 01bf18f92f078308d3ce56c44c1d7226dab116f6a3c0c6b6d8d90c465bc814ff02021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae83ae8541e50a0dd89cc8926d7cf7ca4fbd58a1607fed50c789dd46d302f5d6 0.600000000000 1404251 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 945935, "vin": [ { "gen": { "height": 945925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae83ae8541e50a0dd89cc8926d7cf7ca4fbd58a1607fed50c789dd46d302f5d6" } } ], "extra": [ 1, 191, 24, 249, 47, 7, 131, 8, 211, 206, 86, 196, 76, 29, 114, 38, 218, 177, 22, 246, 163, 192, 198, 182, 216, 217, 12, 70, 91, 200, 20, 255, 2, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8