Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a350eb77544f9158d0f78f96cd4846c819f99951546519f487b1bc17030edd0

Tx prefix hash: 995f82830ddc564a889151137f2b80c084bd4ab489aaaab4a85856ce1b57b149
Tx public key: 9113724a7a8f85c24ef0e3b4aa42a1e05c3a927697c9a729e7ef427d92e68eb8
Timestamp: 1636665976 Timestamp [UCT]: 2021-11-11 21:26:16 Age [y:d:h:m:s]: 03:047:06:59:57
Block: 372358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 812402 RingCT/type: yes/0
Extra: 019113724a7a8f85c24ef0e3b4aa42a1e05c3a927697c9a729e7ef427d92e68eb802110000000c1154028c000000000000000000

1 output(s) for total of 35.830318843000 dcy

stealth address amount amount idx
00: ed6bf246c9dbaf66dd570fdc268332b62c685643bcbfd5cacc8013be4da558f0 35.830318843000 754298 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": 372368, "vin": [ { "gen": { "height": 372358 } } ], "vout": [ { "amount": 35830318843, "target": { "key": "ed6bf246c9dbaf66dd570fdc268332b62c685643bcbfd5cacc8013be4da558f0" } } ], "extra": [ 1, 145, 19, 114, 74, 122, 143, 133, 194, 78, 240, 227, 180, 170, 66, 161, 224, 92, 58, 146, 118, 151, 201, 167, 41, 231, 239, 66, 125, 146, 230, 142, 184, 2, 17, 0, 0, 0, 12, 17, 84, 2, 140, 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