Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ceef78e2542fb00e53da8a1beb74e4cae0047a5ff248ac1d96faf78b76dc1d9

Tx prefix hash: 7c7c99b870ede9e6ec9427b16131ce541f2585c8671c5a08456177d82035c88e
Tx public key: 4508efc8d3456202ebd5a9fc160a1ec4d32a60af81fb222f86ee9ecd18fe3d18
Timestamp: 1721343931 Timestamp [UCT]: 2024-07-18 23:05:31 Age [y:d:h:m:s]: 00:297:04:08:19
Block: 1068711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212310 RingCT/type: yes/0
Extra: 014508efc8d3456202ebd5a9fc160a1ec4d32a60af81fb222f86ee9ecd18fe3d1802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35005cbb2bb417b88cd4f4d9f1156f9b38ad3adf7f648526e7dae9c83e797af6 0.600000000000 1539848 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": 1068721, "vin": [ { "gen": { "height": 1068711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35005cbb2bb417b88cd4f4d9f1156f9b38ad3adf7f648526e7dae9c83e797af6" } } ], "extra": [ 1, 69, 8, 239, 200, 211, 69, 98, 2, 235, 213, 169, 252, 22, 10, 30, 196, 211, 42, 96, 175, 129, 251, 34, 47, 134, 238, 158, 205, 24, 254, 61, 24, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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