Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d38a3f1a733be3f40fcc8d81e77206c77897686567e9d45b509fa46f05fd4e22

Tx prefix hash: 7edc391a37428a7214544d0bd2c5eabe25958063b8f047c7acd70b6cf991f53d
Tx public key: d26b86a52cb11ba4daed864dba32b3d61500b1b5eb311bcfb079fcd64c9cdb9f
Timestamp: 1737111219 Timestamp [UCT]: 2025-01-17 10:53:39 Age [y:d:h:m:s]: 00:153:03:33:48
Block: 1199270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109154 RingCT/type: yes/0
Extra: 01d26b86a52cb11ba4daed864dba32b3d61500b1b5eb311bcfb079fcd64c9cdb9f0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cbb462f7e624ca6c148dfb65d12d8f950667160397ce9d19dab372ca8e678c6 0.600000000000 1685899 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": 1199280, "vin": [ { "gen": { "height": 1199270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cbb462f7e624ca6c148dfb65d12d8f950667160397ce9d19dab372ca8e678c6" } } ], "extra": [ 1, 210, 107, 134, 165, 44, 177, 27, 164, 218, 237, 134, 77, 186, 50, 179, 214, 21, 0, 177, 181, 235, 49, 27, 207, 176, 121, 252, 214, 76, 156, 219, 159, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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