Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f2be881044b313388e9a057d249f0e783555eecf3c7a6a980c90988c8ff8259

Tx prefix hash: 47d30922859f59c706d12a45a454da80b9bb0f9a7c6a629670459b6517f8dad0
Tx public key: aa3be23374764e7622c3ded47ed2ec77139ef615c00f8d118681162b3dbcd950
Timestamp: 1694768910 Timestamp [UCT]: 2023-09-15 09:08:30 Age [y:d:h:m:s]: 01:167:18:29:03
Block: 848560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380964 RingCT/type: yes/0
Extra: 01aa3be23374764e7622c3ded47ed2ec77139ef615c00f8d118681162b3dbcd950021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.947040441000 dcy

stealth address amount amount idx
00: eeda2a20a16a997e5c35db1b16ab603aae36b605b845ddcd0bcd6995a6a5fb77 0.947040441000 1302172 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": 848570, "vin": [ { "gen": { "height": 848560 } } ], "vout": [ { "amount": 947040441, "target": { "key": "eeda2a20a16a997e5c35db1b16ab603aae36b605b845ddcd0bcd6995a6a5fb77" } } ], "extra": [ 1, 170, 59, 226, 51, 116, 118, 78, 118, 34, 195, 222, 212, 126, 210, 236, 119, 19, 158, 246, 21, 192, 15, 141, 17, 134, 129, 22, 43, 61, 188, 217, 80, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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