Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd67bc165accba2572a2ad359f46a41473984390084b98b0324177c29d4f14e0

Tx prefix hash: a937a986b6551c3d9d3a76e6fbb92ec5205e75cccc5e2afca03d3849c2306b42
Tx public key: 4d02c4a6257c96918d416c47503ba8d6b54355af3c1fbfc1288e3be5a10628f6
Timestamp: 1747248501 Timestamp [UCT]: 2025-05-14 18:48:21 Age [y:d:h:m:s]: 00:239:02:24:39
Block: 1282937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168652 RingCT/type: yes/0
Extra: 014d02c4a6257c96918d416c47503ba8d6b54355af3c1fbfc1288e3be5a10628f602110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a2bef5588e33e9ef43419516ee29fa971fe9d26d0b1418ebff4d7a530676ace 0.600000000000 1770352 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": 1282947, "vin": [ { "gen": { "height": 1282937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a2bef5588e33e9ef43419516ee29fa971fe9d26d0b1418ebff4d7a530676ace" } } ], "extra": [ 1, 77, 2, 196, 166, 37, 124, 150, 145, 141, 65, 108, 71, 80, 59, 168, 214, 181, 67, 85, 175, 60, 31, 191, 193, 40, 142, 59, 229, 161, 6, 40, 246, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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