Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a0e4103ad86851953051d6231027aa5b5765dc30e533fb6fccbb02a5d60f353

Tx prefix hash: bbfbc5286aff4005e324b19ec41deefabb253ec69e82b68d585f0825f0826452
Tx public key: 474a54e60491ae4cdc28c6ca72881eb48f6aa5c6e448f4cc5c334999b297f74a
Timestamp: 1700645044 Timestamp [UCT]: 2023-11-22 09:24:04 Age [y:d:h:m:s]: 01:148:02:56:08
Block: 897091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367048 RingCT/type: yes/0
Extra: 01474a54e60491ae4cdc28c6ca72881eb48f6aa5c6e448f4cc5c334999b297f74a02110000000975e3f0e9000000000000000000

1 output(s) for total of 0.653980960000 dcy

stealth address amount amount idx
00: bf6fcebda69a7c66de58a74dc64eb367fa004eeef014e636a94370b2e306a511 0.653980960000 1353456 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": 897101, "vin": [ { "gen": { "height": 897091 } } ], "vout": [ { "amount": 653980960, "target": { "key": "bf6fcebda69a7c66de58a74dc64eb367fa004eeef014e636a94370b2e306a511" } } ], "extra": [ 1, 71, 74, 84, 230, 4, 145, 174, 76, 220, 40, 198, 202, 114, 136, 30, 180, 143, 106, 165, 198, 228, 72, 244, 204, 92, 51, 73, 153, 178, 151, 247, 74, 2, 17, 0, 0, 0, 9, 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