Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7e3441941ab19afa32dd925c4da96abf03662a6182470a21493a25440de97ba

Tx prefix hash: d87d372dc5930cf955f33f2914da76e97e9d138aaf3c99c65bb954131d8f2acf
Tx public key: 48fe2361c12ff8731385e9a5091a1aa99cc3a0fc91c166dd99493565f5f2d97a
Timestamp: 1720880153 Timestamp [UCT]: 2024-07-13 14:15:53 Age [y:d:h:m:s]: 00:225:00:14:17
Block: 1064867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160688 RingCT/type: yes/0
Extra: 0148fe2361c12ff8731385e9a5091a1aa99cc3a0fc91c166dd99493565f5f2d97a02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5259f0a59ce133f2fb0b0a0288a50242b5637670c6e3c7a3b6f993ae3fbc6f2 0.600000000000 1535406 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": 1064877, "vin": [ { "gen": { "height": 1064867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5259f0a59ce133f2fb0b0a0288a50242b5637670c6e3c7a3b6f993ae3fbc6f2" } } ], "extra": [ 1, 72, 254, 35, 97, 193, 47, 248, 115, 19, 133, 233, 165, 9, 26, 26, 169, 156, 195, 160, 252, 145, 193, 102, 221, 153, 73, 53, 101, 245, 242, 217, 122, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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