Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ca03d17d11319e07ded38ac38455f8554f6aecd99523005562a335bcc1c043e

Tx prefix hash: fd51f83c05c7bd4afc1743573ba90e07596072c737bc0854add45dbc220ef713
Tx public key: 14e81dc9c28c1bea532037aa8df35ed1bf512f8c4dfd8cedb346367fb01a2099
Timestamp: 1720245197 Timestamp [UCT]: 2024-07-06 05:53:17 Age [y:d:h:m:s]: 00:251:19:02:22
Block: 1059586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179910 RingCT/type: yes/0
Extra: 0114e81dc9c28c1bea532037aa8df35ed1bf512f8c4dfd8cedb346367fb01a209902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a1967598115cf715719b1f8f249682041476331e2d25e84f188fc76d862e5b7 0.600000000000 1530055 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": 1059596, "vin": [ { "gen": { "height": 1059586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a1967598115cf715719b1f8f249682041476331e2d25e84f188fc76d862e5b7" } } ], "extra": [ 1, 20, 232, 29, 201, 194, 140, 27, 234, 83, 32, 55, 170, 141, 243, 94, 209, 191, 81, 47, 140, 77, 253, 140, 237, 179, 70, 54, 127, 176, 26, 32, 153, 2, 17, 0, 0, 0, 2, 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