Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4175ac3762db762de71e64a8dfa7506a8bc7ef3cb3fb8b2a872dfa5fe509d987

Tx prefix hash: 30a160b1525c8ce5db7f5229d8ac3e22ed5f77971ebd7dabe9ea7c364ab341e5
Tx public key: d1d2b210963a0498c3ca189d47a76d90185ddff90cabec8899bd2f7ea0ecc02e
Timestamp: 1718315541 Timestamp [UCT]: 2024-06-13 21:52:21 Age [y:d:h:m:s]: 00:305:02:27:14
Block: 1043595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218027 RingCT/type: yes/0
Extra: 01d1d2b210963a0498c3ca189d47a76d90185ddff90cabec8899bd2f7ea0ecc02e02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2ba5639c3eca9e3ff41e10e8beea5218d046b0eb632cde5cabfbf7784141274 0.600000000000 1512752 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": 1043605, "vin": [ { "gen": { "height": 1043595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2ba5639c3eca9e3ff41e10e8beea5218d046b0eb632cde5cabfbf7784141274" } } ], "extra": [ 1, 209, 210, 178, 16, 150, 58, 4, 152, 195, 202, 24, 157, 71, 167, 109, 144, 24, 93, 223, 249, 12, 171, 236, 136, 153, 189, 47, 126, 160, 236, 192, 46, 2, 17, 0, 0, 0, 5, 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