Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62c35821c33323f85ba23d6b5ac5dc39ffaaa90b372a52a6035067f9dd33b3c6

Tx prefix hash: 5635318a8d700757061d9ff5915296affcef8e33fdd1c3acc1b520ba6409470f
Tx public key: 2182340b0d97683c08affaef36e9ff8b8e6a57ebf715f522eae68fbc217d0f82
Timestamp: 1729038755 Timestamp [UCT]: 2024-10-16 00:32:35 Age [y:d:h:m:s]: 00:193:08:11:18
Block: 1132512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137952 RingCT/type: yes/0
Extra: 012182340b0d97683c08affaef36e9ff8b8e6a57ebf715f522eae68fbc217d0f8202110000000a3cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9114e353953b55bd189e92e3e5fdc4aed60bc18124f7588b5ca2f2f17c5550bd 0.600000000000 1615437 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": 1132522, "vin": [ { "gen": { "height": 1132512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9114e353953b55bd189e92e3e5fdc4aed60bc18124f7588b5ca2f2f17c5550bd" } } ], "extra": [ 1, 33, 130, 52, 11, 13, 151, 104, 60, 8, 175, 250, 239, 54, 233, 255, 139, 142, 106, 87, 235, 247, 21, 245, 34, 234, 230, 143, 188, 33, 125, 15, 130, 2, 17, 0, 0, 0, 10, 60, 208, 252, 6, 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