Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddd6db229359a16ce8c4f2534d7ca0f67d7772493d3c7f1c76e87dade3e3f247

Tx prefix hash: 5bb7ac8d1ef5f13c6289d630f4f8a35ce7b884dee53195f48a7c0a6b1311891e
Tx public key: 865bdbe2c759e4d075941220ccc2c8cd33853ffc7712b376ca1d04479b77c8e2
Timestamp: 1710052703 Timestamp [UCT]: 2024-03-10 06:38:23 Age [y:d:h:m:s]: 01:056:13:23:07
Block: 975099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301421 RingCT/type: yes/0
Extra: 01865bdbe2c759e4d075941220ccc2c8cd33853ffc7712b376ca1d04479b77c8e202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fa41fc1cd2d6ec8b157d9343f3d740adc9e3078de5c09a29e714d601d0c5716 0.600000000000 1435070 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": 975109, "vin": [ { "gen": { "height": 975099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fa41fc1cd2d6ec8b157d9343f3d740adc9e3078de5c09a29e714d601d0c5716" } } ], "extra": [ 1, 134, 91, 219, 226, 199, 89, 228, 208, 117, 148, 18, 32, 204, 194, 200, 205, 51, 133, 63, 252, 119, 18, 179, 118, 202, 29, 4, 71, 155, 119, 200, 226, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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