Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22621fd99d4284f107db38f2746edc4da6ffeca5afc70c412859eabebcb62cb9

Tx prefix hash: 56cabe39af91610143944cf10dd287adf0fd9aa88ff277b6c88b176815d44cef
Tx public key: 9a34408e3f0b6ed26b08e7ee68426ee7fc532aa6e77c62d9d0b92a2353f224e7
Timestamp: 1736718710 Timestamp [UCT]: 2025-01-12 21:51:50 Age [y:d:h:m:s]: 00:156:18:08:27
Block: 1196017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111744 RingCT/type: yes/0
Extra: 019a34408e3f0b6ed26b08e7ee68426ee7fc532aa6e77c62d9d0b92a2353f224e70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 078bcf5c3591967bee5f30f87b72f044eb67a1b8087e1ae3faf07a7152142352 0.600000000000 1682614 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": 1196027, "vin": [ { "gen": { "height": 1196017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "078bcf5c3591967bee5f30f87b72f044eb67a1b8087e1ae3faf07a7152142352" } } ], "extra": [ 1, 154, 52, 64, 142, 63, 11, 110, 210, 107, 8, 231, 238, 104, 66, 110, 231, 252, 83, 42, 166, 231, 124, 98, 217, 208, 185, 42, 35, 83, 242, 36, 231, 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