Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dc5450fdc3e4d36c8ab3ff7e9c6da27a17f9c6144801d68380338672c7e94eb

Tx prefix hash: 6eae6320c6443f44726cb317b2f1873954aa256f958ca9ecec7d5d827c0144c9
Tx public key: 5477de1813b584cd4851bc636577aeb0ccda7c0d305f243ef3e8830447a4352e
Timestamp: 1741577050 Timestamp [UCT]: 2025-03-10 03:24:10 Age [y:d:h:m:s]: 00:256:17:53:04
Block: 1235984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181230 RingCT/type: yes/0
Extra: 015477de1813b584cd4851bc636577aeb0ccda7c0d305f243ef3e8830447a4352e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0ea95cd9af887f192c9c96c3298dc0081b12b9caa9e76c28ac948868e0d75e1 0.600000000000 1722929 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": 1235994, "vin": [ { "gen": { "height": 1235984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0ea95cd9af887f192c9c96c3298dc0081b12b9caa9e76c28ac948868e0d75e1" } } ], "extra": [ 1, 84, 119, 222, 24, 19, 181, 132, 205, 72, 81, 188, 99, 101, 119, 174, 176, 204, 218, 124, 13, 48, 95, 36, 62, 243, 232, 131, 4, 71, 164, 53, 46, 2, 17, 0, 0, 0, 5, 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