Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3be41d6a4b3f0cb3764107f7e1645a9cbe100de3392a8fb7a954de5da628b5a

Tx prefix hash: 345de2e26f9fee03c56b3066cff14ba997bc71b5be90fe0e554b5863bf5efc26
Tx public key: e9395b1434bb89e87aab0e25784c77a3b9d2768a3f2c513f70fd58cc52a186f6
Timestamp: 1729297809 Timestamp [UCT]: 2024-10-19 00:30:09 Age [y:d:h:m:s]: 00:167:19:16:04
Block: 1134635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119698 RingCT/type: yes/0
Extra: 01e9395b1434bb89e87aab0e25784c77a3b9d2768a3f2c513f70fd58cc52a186f60211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9f9217422d0dc2dc43a78fe3dd52c88c1d9e58a9ec8d63acc6faa72cea28862 0.600000000000 1617960 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": 1134645, "vin": [ { "gen": { "height": 1134635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9f9217422d0dc2dc43a78fe3dd52c88c1d9e58a9ec8d63acc6faa72cea28862" } } ], "extra": [ 1, 233, 57, 91, 20, 52, 187, 137, 232, 122, 171, 14, 37, 120, 76, 119, 163, 185, 210, 118, 138, 63, 44, 81, 63, 112, 253, 88, 204, 82, 161, 134, 246, 2, 17, 0, 0, 0, 2, 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