Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01d8323a0ceee5afe16a1ecce683cddf3b64b86de07d4aa256d59794354b3ba1

Tx prefix hash: 1099867aecd2974ce7ea59df177f073fc295cdb8f7825fbc72154124a64d4496
Tx public key: 3f5aa807594a029a73edf50f834acc17ed7358569f78c931cf4f0e8e78827f8f
Timestamp: 1719252314 Timestamp [UCT]: 2024-06-24 18:05:14 Age [y:d:h:m:s]: 01:138:05:09:45
Block: 1051343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357345 RingCT/type: yes/0
Extra: 013f5aa807594a029a73edf50f834acc17ed7358569f78c931cf4f0e8e78827f8f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 456bb371ba992d191758a7b65b162f5e6967d274f3c81d52a4a8b5047fa86586 0.600000000000 1521654 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": 1051353, "vin": [ { "gen": { "height": 1051343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "456bb371ba992d191758a7b65b162f5e6967d274f3c81d52a4a8b5047fa86586" } } ], "extra": [ 1, 63, 90, 168, 7, 89, 74, 2, 154, 115, 237, 245, 15, 131, 74, 204, 23, 237, 115, 88, 86, 159, 120, 201, 49, 207, 79, 14, 142, 120, 130, 127, 143, 2, 17, 0, 0, 0, 2, 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