Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b4dd2fa524d2c7abf23aa8f2304f5d2cd0a0c30f74290c64eba28cd0cc4c8b7

Tx prefix hash: 30a385ee536c14c68de650a3c24a6796249ba536a5d49a43677267d03843de84
Tx public key: 4d17e56a9856e3bd2992dd14ef9fb57e6caef63b6d1ddb2c53174aa25876b7f6
Timestamp: 1684771611 Timestamp [UCT]: 2023-05-22 16:06:51 Age [y:d:h:m:s]: 02:225:18:55:24
Block: 765750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 681242 RingCT/type: yes/0
Extra: 014d17e56a9856e3bd2992dd14ef9fb57e6caef63b6d1ddb2c53174aa25876b7f602110000000375e3f0e9000000000000000000

1 output(s) for total of 1.781363511000 dcy

stealth address amount amount idx
00: 557e0c4d3bfd89dfc16d233a00ceedb25f4d8dbe6f5cd6c313ffef148872cfc4 1.781363511000 1214753 of 0

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": 765760, "vin": [ { "gen": { "height": 765750 } } ], "vout": [ { "amount": 1781363511, "target": { "key": "557e0c4d3bfd89dfc16d233a00ceedb25f4d8dbe6f5cd6c313ffef148872cfc4" } } ], "extra": [ 1, 77, 23, 229, 106, 152, 86, 227, 189, 41, 146, 221, 20, 239, 159, 181, 126, 108, 174, 246, 59, 109, 29, 219, 44, 83, 23, 74, 162, 88, 118, 183, 246, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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