Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05bb93390718b08bff434e690f474a6d50c942fe6846d5fefd0b7e4666fb82e1

Tx prefix hash: df9b85737b5602f20bee220b49e72dd8d5bf25e0e0d56986f498756eb87aeb25
Tx public key: 8f3c06968ccb6b56b8052ff6eb833cc8442b255dbf14e0e9c4db61bb2eeb43e3
Timestamp: 1710247267 Timestamp [UCT]: 2024-03-12 12:41:07 Age [y:d:h:m:s]: 01:060:04:16:26
Block: 976717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304002 RingCT/type: yes/0
Extra: 018f3c06968ccb6b56b8052ff6eb833cc8442b255dbf14e0e9c4db61bb2eeb43e30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baf523f04249da498579c0a1bc4b30a850bcd519c930f36dcb449cfd2304b6ca 0.600000000000 1436712 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": 976727, "vin": [ { "gen": { "height": 976717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baf523f04249da498579c0a1bc4b30a850bcd519c930f36dcb449cfd2304b6ca" } } ], "extra": [ 1, 143, 60, 6, 150, 140, 203, 107, 86, 184, 5, 47, 246, 235, 131, 60, 200, 68, 43, 37, 93, 191, 20, 224, 233, 196, 219, 97, 187, 46, 235, 67, 227, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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