Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6872a0219c5ac9d17b797f87bd551152d39a892b1608341b3b5f1f3b1b7d9751

Tx prefix hash: 1b8d22dd0fdb643007ecfb92bd32188880f8728a1aa4d0fc5065cf7e220fd8e1
Tx public key: 8cd163cc452e9cf783e56549805734ca8b954c3df28e9fc8cb64f9eaa345c294
Timestamp: 1737638473 Timestamp [UCT]: 2025-01-23 13:21:13 Age [y:d:h:m:s]: 00:292:06:36:07
Block: 1203590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206429 RingCT/type: yes/0
Extra: 018cd163cc452e9cf783e56549805734ca8b954c3df28e9fc8cb64f9eaa345c294021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dfe682f0fa07ddd010bd7701c5ca07f2443618b8f9566aebf51d8685a46891f 0.600000000000 1690267 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": 1203600, "vin": [ { "gen": { "height": 1203590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dfe682f0fa07ddd010bd7701c5ca07f2443618b8f9566aebf51d8685a46891f" } } ], "extra": [ 1, 140, 209, 99, 204, 69, 46, 156, 247, 131, 229, 101, 73, 128, 87, 52, 202, 139, 149, 76, 61, 242, 142, 159, 200, 203, 100, 249, 234, 163, 69, 194, 148, 2, 17, 0, 0, 0, 4, 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