Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36d8efb07f4ba3115a9e8d003fdb1131d0196e4390c449f133539365a734cf2a

Tx prefix hash: 59ecef7af4819acf95145d20fde60dcd5c6deb43222c64dfd1b5473c5a429226
Tx public key: dd5db43f07502c052ea19ff3b61f8b2f610971c8065b89a8db451d12556816b9
Timestamp: 1703193214 Timestamp [UCT]: 2023-12-21 21:13:34 Age [y:d:h:m:s]: 01:109:22:32:46
Block: 918214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339698 RingCT/type: yes/0
Extra: 01dd5db43f07502c052ea19ff3b61f8b2f610971c8065b89a8db451d12556816b902110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 104d9ed9318ce02d9ff88b933b2302e7eaaf1d8fb5f19bda0ab11290364c36f8 0.600000000000 1375856 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": 918224, "vin": [ { "gen": { "height": 918214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "104d9ed9318ce02d9ff88b933b2302e7eaaf1d8fb5f19bda0ab11290364c36f8" } } ], "extra": [ 1, 221, 93, 180, 63, 7, 80, 44, 5, 46, 161, 159, 243, 182, 31, 139, 47, 97, 9, 113, 200, 6, 91, 137, 168, 219, 69, 29, 18, 85, 104, 22, 185, 2, 17, 0, 0, 0, 8, 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