Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9263f612ff986add4be32ed527d241864a72bdc10d8e44cd79fa2e5557d79432

Tx prefix hash: 7d176173bc765d16c15681aebd046dd26980c6a3d92b9d5de34e740ea60883ae
Tx public key: ec7eb9ebe8258de17e954a205d3ca16fe8fcd82e4db96ce4ce841f99b8dce2c6
Timestamp: 1732571127 Timestamp [UCT]: 2024-11-25 21:45:27 Age [y:d:h:m:s]: 01:006:18:01:30
Block: 1161678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263257 RingCT/type: yes/0
Extra: 01ec7eb9ebe8258de17e954a205d3ca16fe8fcd82e4db96ce4ce841f99b8dce2c6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5dff4680dac621f3178a7d18ce5cb818c5a599cdfafd3e35fbae53feaf516fc 0.600000000000 1647333 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": 1161688, "vin": [ { "gen": { "height": 1161678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5dff4680dac621f3178a7d18ce5cb818c5a599cdfafd3e35fbae53feaf516fc" } } ], "extra": [ 1, 236, 126, 185, 235, 232, 37, 141, 225, 126, 149, 74, 32, 93, 60, 161, 111, 232, 252, 216, 46, 77, 185, 108, 228, 206, 132, 31, 153, 184, 220, 226, 198, 2, 17, 0, 0, 0, 3, 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