Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 722ef5d7281b8ef664f0a846a2b8377ccc7f6d130263c8a2fcabd4e82aab48c4

Tx prefix hash: c3beaeb06e68f8d53224fa214a7aa43bea7066be4b609123fe88010d1c63c8e6
Tx public key: 4ecbf470edfde874ad62e84c2a2c3c9417f673def6290b19bf224d4c6089c2b9
Timestamp: 1725327710 Timestamp [UCT]: 2024-09-03 01:41:50 Age [y:d:h:m:s]: 00:209:14:12:54
Block: 1101723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149642 RingCT/type: yes/0
Extra: 014ecbf470edfde874ad62e84c2a2c3c9417f673def6290b19bf224d4c6089c2b9021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7877537e5d961f113c02d94060f7d6402e4df79dc36adb9c48708e4143c2d6ca 0.600000000000 1577882 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": 1101733, "vin": [ { "gen": { "height": 1101723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7877537e5d961f113c02d94060f7d6402e4df79dc36adb9c48708e4143c2d6ca" } } ], "extra": [ 1, 78, 203, 244, 112, 237, 253, 232, 116, 173, 98, 232, 76, 42, 44, 60, 148, 23, 246, 115, 222, 246, 41, 11, 25, 191, 34, 77, 76, 96, 137, 194, 185, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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