Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42d03fb7e8508861a9765cc30097c24aa469a677cb00c03482f9ee9ada4b90b1

Tx prefix hash: ac3996419cc8d46e93d404b3f8060ba72f01e8cea59294e10bc78c7b52dd81fa
Tx public key: 3823a533c396d443721458f574634cfed5c48cec68cf3b1f5ed16cb7e62b1037
Timestamp: 1736704576 Timestamp [UCT]: 2025-01-12 17:56:16 Age [y:d:h:m:s]: 00:063:18:32:06
Block: 1195904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45365 RingCT/type: yes/0
Extra: 013823a533c396d443721458f574634cfed5c48cec68cf3b1f5ed16cb7e62b10370211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 679d1b4b0e3a3d7a1f226e6078b7698fad6b5d3d60751c5a5378ef0895741ba5 0.600000000000 1682497 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": 1195914, "vin": [ { "gen": { "height": 1195904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "679d1b4b0e3a3d7a1f226e6078b7698fad6b5d3d60751c5a5378ef0895741ba5" } } ], "extra": [ 1, 56, 35, 165, 51, 195, 150, 212, 67, 114, 20, 88, 245, 116, 99, 76, 254, 213, 196, 140, 236, 104, 207, 59, 31, 94, 209, 108, 183, 230, 43, 16, 55, 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