Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03aba150836f3445e04d275b2973d1953e0bbbe2c57565044b8c5d8ba2e6a0fd

Tx prefix hash: 94c5d5b3653eb35a2a883ee2346675d02d1ed0de4b691d430d01a82cc646197a
Tx public key: 00df4fec577c1dcd46c300a1e94d10e526a0cabe3cf652fbc73c29a41432346e
Timestamp: 1735204999 Timestamp [UCT]: 2024-12-26 09:23:19 Age [y:d:h:m:s]: 00:085:20:06:38
Block: 1183496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61122 RingCT/type: yes/0
Extra: 0100df4fec577c1dcd46c300a1e94d10e526a0cabe3cf652fbc73c29a41432346e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c80dc8b5577913a749dcb07437525c0a2491c505b8fcd7fd571c20d0b1e6bfec 0.600000000000 1669941 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": 1183506, "vin": [ { "gen": { "height": 1183496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c80dc8b5577913a749dcb07437525c0a2491c505b8fcd7fd571c20d0b1e6bfec" } } ], "extra": [ 1, 0, 223, 79, 236, 87, 124, 29, 205, 70, 195, 0, 161, 233, 77, 16, 229, 38, 160, 202, 190, 60, 246, 82, 251, 199, 60, 41, 164, 20, 50, 52, 110, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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