Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10b3cb14ba3370daf6878e94d728adf2502de6507ca4a56726d1bb9b7f5eca38

Tx prefix hash: b0a1f2899d31838fd60a81bbc21745518134327e8dab939b330ca0bf259045b3
Tx public key: a270b1de8ea8a4896c29dca74a05c484b418ebab719aaf38ec9ca2297e1a0249
Timestamp: 1725941424 Timestamp [UCT]: 2024-09-10 04:10:24 Age [y:d:h:m:s]: 00:103:14:17:12
Block: 1106812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74116 RingCT/type: yes/0
Extra: 01a270b1de8ea8a4896c29dca74a05c484b418ebab719aaf38ec9ca2297e1a0249021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a60c1307f766f9f3b851569b4088b5f7b671c6ab97f1061957f43a3428de45aa 0.600000000000 1584413 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": 1106822, "vin": [ { "gen": { "height": 1106812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a60c1307f766f9f3b851569b4088b5f7b671c6ab97f1061957f43a3428de45aa" } } ], "extra": [ 1, 162, 112, 177, 222, 142, 168, 164, 137, 108, 41, 220, 167, 74, 5, 196, 132, 180, 24, 235, 171, 113, 154, 175, 56, 236, 156, 162, 41, 126, 26, 2, 73, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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