Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7031cf772783db28a46ead51ec9b8fd80dbe39240ac0e779f808294ba5cdba8

Tx prefix hash: a44b1811640556e513a9606d3d9326a65075a3cba141e5d818453603df151d2f
Tx public key: 48c5cdd4fa055e2cee02eb36f383a0b395a4a4ee617aac34a17e58aa2a4971d3
Timestamp: 1705226704 Timestamp [UCT]: 2024-01-14 10:05:04 Age [y:d:h:m:s]: 01:298:17:05:57
Block: 935073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472300 RingCT/type: yes/0
Extra: 0148c5cdd4fa055e2cee02eb36f383a0b395a4a4ee617aac34a17e58aa2a4971d3021100000004679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a9e042f04fcf77d8968c9cbd2741eff78d43b79fb0076628744e8ff8bf681ec 0.600000000000 1393089 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": 935083, "vin": [ { "gen": { "height": 935073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a9e042f04fcf77d8968c9cbd2741eff78d43b79fb0076628744e8ff8bf681ec" } } ], "extra": [ 1, 72, 197, 205, 212, 250, 5, 94, 44, 238, 2, 235, 54, 243, 131, 160, 179, 149, 164, 164, 238, 97, 122, 172, 52, 161, 126, 88, 170, 42, 73, 113, 211, 2, 17, 0, 0, 0, 4, 103, 154, 138, 129, 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