Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a8034ea9c85a0e7574374863ab5f76a785c34155e3186417701bcc319ea76a3

Tx prefix hash: b042de398bbbc42cc59d3330f3cc3fa0d977df709f59091dd2aa6fe537a5c700
Tx public key: 2cb51c233a1b8f36997874fd932919c47370f84bd2c712e097ed59eec50cf353
Timestamp: 1730677135 Timestamp [UCT]: 2024-11-03 23:38:55 Age [y:d:h:m:s]: 00:149:09:15:39
Block: 1145996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106583 RingCT/type: yes/0
Extra: 012cb51c233a1b8f36997874fd932919c47370f84bd2c712e097ed59eec50cf3530211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fd18fef4e77f9225c3406faf108ff5cc5b3b2f0bdbff8b0c45217b7e3b7df49 0.600000000000 1630541 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": 1146006, "vin": [ { "gen": { "height": 1145996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fd18fef4e77f9225c3406faf108ff5cc5b3b2f0bdbff8b0c45217b7e3b7df49" } } ], "extra": [ 1, 44, 181, 28, 35, 58, 27, 143, 54, 153, 120, 116, 253, 147, 41, 25, 196, 115, 112, 248, 75, 210, 199, 18, 224, 151, 237, 89, 238, 197, 12, 243, 83, 2, 17, 0, 0, 0, 3, 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