Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 104434e0546a1b057980eaaae4790b67492a9cf1672ecc6253137fea8dbb6611

Tx prefix hash: f29dbf16a04c6acc7d947f59ded9d1555b47b5fd2e66284a9051a15088d894ff
Tx public key: 499717b80d1be7535b2a94e89e1be07e90b66e3b4e09b71f229d93b9a2b82f1a
Timestamp: 1762767778 Timestamp [UCT]: 2025-11-10 09:42:58 Age [y:d:h:m:s]: 00:011:11:37:20
Block: 1408994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8223 RingCT/type: yes/0
Extra: 01499717b80d1be7535b2a94e89e1be07e90b66e3b4e09b71f229d93b9a2b82f1a02110000000701491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98bf70af24ab745bcc23a74766a336f954c5dee282b6b7c416bf20220cda6d38 0.600000000000 1897425 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": 1409004, "vin": [ { "gen": { "height": 1408994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98bf70af24ab745bcc23a74766a336f954c5dee282b6b7c416bf20220cda6d38" } } ], "extra": [ 1, 73, 151, 23, 184, 13, 27, 231, 83, 91, 42, 148, 232, 158, 27, 224, 126, 144, 182, 110, 59, 78, 9, 183, 31, 34, 157, 147, 185, 162, 184, 47, 26, 2, 17, 0, 0, 0, 7, 1, 73, 31, 136, 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