Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1183aa2e108706a9d7ba990c16e4bbeebef775f0fe51e212ad4675f6e317ca8

Tx prefix hash: 240dde0c1e452aceab2e1c96798326f35f8786129b6c52e0d4e81c874115e31f
Tx public key: 6a83c8cd83e0477342f0120417b2aaee2d19575f19f2d6088b57dd7f458f9b31
Timestamp: 1731507441 Timestamp [UCT]: 2024-11-13 14:17:21 Age [y:d:h:m:s]: 00:146:05:46:54
Block: 1152869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104337 RingCT/type: yes/0
Extra: 016a83c8cd83e0477342f0120417b2aaee2d19575f19f2d6088b57dd7f458f9b310211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff01bf0a6340adb46634ff2c75b3b8656149b640a295caa1e8e177b1d5418b89 0.600000000000 1638474 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": 1152879, "vin": [ { "gen": { "height": 1152869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff01bf0a6340adb46634ff2c75b3b8656149b640a295caa1e8e177b1d5418b89" } } ], "extra": [ 1, 106, 131, 200, 205, 131, 224, 71, 115, 66, 240, 18, 4, 23, 178, 170, 238, 45, 25, 87, 95, 25, 242, 214, 8, 139, 87, 221, 127, 69, 143, 155, 49, 2, 17, 0, 0, 0, 4, 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