Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74dec0c1032d6d7a2d9b108cea72b9b10235c16810c2896beee5196f238dc4a0

Tx prefix hash: 939dc1ce337b02c2a6294eef38ea12e3729f3c6e882a1d7f5fb32255a338569a
Tx public key: b0494909e886719c47a43d3f71ad3f996b55044f54452b66a66dcfa3d68f2618
Timestamp: 1746239463 Timestamp [UCT]: 2025-05-03 02:31:03 Age [y:d:h:m:s]: 00:202:16:16:44
Block: 1274575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142564 RingCT/type: yes/0
Extra: 01b0494909e886719c47a43d3f71ad3f996b55044f54452b66a66dcfa3d68f2618021100000005dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a38fa7d385931db2ae4f0b3c8bbe87eec83e65807697a7ae6ecb5fe9178c060f 0.600000000000 1761870 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": 1274585, "vin": [ { "gen": { "height": 1274575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a38fa7d385931db2ae4f0b3c8bbe87eec83e65807697a7ae6ecb5fe9178c060f" } } ], "extra": [ 1, 176, 73, 73, 9, 232, 134, 113, 156, 71, 164, 61, 63, 113, 173, 63, 153, 107, 85, 4, 79, 84, 69, 43, 102, 166, 109, 207, 163, 214, 143, 38, 24, 2, 17, 0, 0, 0, 5, 223, 195, 186, 73, 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