Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06f8ef03cf3911eb8a4f98b8f8a9455a437ab673e92bffe8fa8bd3028af71456

Tx prefix hash: bfc664ab28e9d037f87e0fee954c3052491ec8f0e6b4f4dbbc6808399c9e3e9e
Tx public key: 561b40fd6ed4c2cc2403d82afd8f1affe261775fd2e3ac00a4dc7d688a31ae5e
Timestamp: 1578077429 Timestamp [UCT]: 2020-01-03 18:50:29 Age [y:d:h:m:s]: 05:096:18:48:15
Block: 37911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1219103 RingCT/type: yes/0
Extra: 01561b40fd6ed4c2cc2403d82afd8f1affe261775fd2e3ac00a4dc7d688a31ae5e021100000010dafe52e4000000000000000000

1 output(s) for total of 459.606296816000 dcy

stealth address amount amount idx
00: c81829a4bd8936e9763a241c133f9baf138e0b96f2b4ecf88411490a56f9a465 459.606296816000 64468 of 0

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": 37921, "vin": [ { "gen": { "height": 37911 } } ], "vout": [ { "amount": 459606296816, "target": { "key": "c81829a4bd8936e9763a241c133f9baf138e0b96f2b4ecf88411490a56f9a465" } } ], "extra": [ 1, 86, 27, 64, 253, 110, 212, 194, 204, 36, 3, 216, 42, 253, 143, 26, 255, 226, 97, 119, 95, 210, 227, 172, 0, 164, 220, 125, 104, 138, 49, 174, 94, 2, 17, 0, 0, 0, 16, 218, 254, 82, 228, 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