Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0154a78f6cd8066ff57744cde537438a09352759dd5ca5024140d9f01d4c62cd

Tx prefix hash: 0c9d3d4d8e38a6b518cf965cfa2c502757e3551937e4430b277a2195ee2bc437
Tx public key: a4eb9c00f451d341fa6ef194ea9621d74a446aed45f7b44da15b6dc9a52a5152
Timestamp: 1730337837 Timestamp [UCT]: 2024-10-31 01:23:57 Age [y:d:h:m:s]: 01:003:20:22:48
Block: 1143173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261163 RingCT/type: yes/0
Extra: 01a4eb9c00f451d341fa6ef194ea9621d74a446aed45f7b44da15b6dc9a52a515202110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ed7eaa37591020d9d3312756392a89b205f7d1612256d9e89a81f0d7951bf56 0.600000000000 1627036 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": 1143183, "vin": [ { "gen": { "height": 1143173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ed7eaa37591020d9d3312756392a89b205f7d1612256d9e89a81f0d7951bf56" } } ], "extra": [ 1, 164, 235, 156, 0, 244, 81, 211, 65, 250, 110, 241, 148, 234, 150, 33, 215, 74, 68, 106, 237, 69, 247, 180, 77, 161, 91, 109, 201, 165, 42, 81, 82, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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