Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aade1c5975b86e93bc15953d590c74c7037eb5b2b9d91951c1c74807dcc581e

Tx prefix hash: c806ec1c8a26029b26c09354c24f720c3dba0df1af728069566f6d635b692075
Tx public key: d8f4e8534afa1afe8d418c10f23b6630ab4eedc470a54a8d7608d1eb4ff23547
Timestamp: 1725029615 Timestamp [UCT]: 2024-08-30 14:53:35 Age [y:d:h:m:s]: 00:272:14:04:55
Block: 1099244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194724 RingCT/type: yes/0
Extra: 01d8f4e8534afa1afe8d418c10f23b6630ab4eedc470a54a8d7608d1eb4ff23547021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87f8b1ef073d0f878296834ae8742edeaea82d4024ec5cc317d3ff4ce0101359 0.600000000000 1575191 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": 1099254, "vin": [ { "gen": { "height": 1099244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87f8b1ef073d0f878296834ae8742edeaea82d4024ec5cc317d3ff4ce0101359" } } ], "extra": [ 1, 216, 244, 232, 83, 74, 250, 26, 254, 141, 65, 140, 16, 242, 59, 102, 48, 171, 78, 237, 196, 112, 165, 74, 141, 118, 8, 209, 235, 79, 242, 53, 71, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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