Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5445a54631c553d24cffb5982969b9a65061f56da8baef76e460fef487c3358e

Tx prefix hash: c8b097fedc884fde1ed1413a45bb78a2f0e7ef4e68b66b507a5687011dc77ab5
Tx public key: 3e3ff63b6d1606f2218d0d77ecd37def1a3e065a37994cf894d6c4209b5c1517
Timestamp: 1710597664 Timestamp [UCT]: 2024-03-16 14:01:04 Age [y:d:h:m:s]: 01:077:20:09:07
Block: 979622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316647 RingCT/type: yes/0
Extra: 013e3ff63b6d1606f2218d0d77ecd37def1a3e065a37994cf894d6c4209b5c151702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7200526171272f070904fb12754ba30b913f7adcde4011f91583d52b4a1afcb3 0.600000000000 1439661 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": 979632, "vin": [ { "gen": { "height": 979622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7200526171272f070904fb12754ba30b913f7adcde4011f91583d52b4a1afcb3" } } ], "extra": [ 1, 62, 63, 246, 59, 109, 22, 6, 242, 33, 141, 13, 119, 236, 211, 125, 239, 26, 62, 6, 90, 55, 153, 76, 248, 148, 214, 196, 32, 155, 92, 21, 23, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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