Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12056365ab8a3cb45df9b67dea8209e76666ea8155fe3f8767a1379e0d12442a

Tx prefix hash: 94ccedfb1db9250c12b4fb64cbb5bb8305694ad862f7002185fd9408635d2a2f
Tx public key: 4d6dfc56f5edf4ab01c6e3151db01133890cbd8c90b28afdf74184cd39a2b4e2
Timestamp: 1760150835 Timestamp [UCT]: 2025-10-11 02:47:15 Age [y:d:h:m:s]: 00:047:10:19:10
Block: 1387304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33970 RingCT/type: yes/0
Extra: 014d6dfc56f5edf4ab01c6e3151db01133890cbd8c90b28afdf74184cd39a2b4e202110000000297baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 395cc6f3ba15ffb0474e41eb8e2e1ad99916e3f36f6eb20e7dab4c04797895f3 0.600000000000 1875491 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": 1387314, "vin": [ { "gen": { "height": 1387304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "395cc6f3ba15ffb0474e41eb8e2e1ad99916e3f36f6eb20e7dab4c04797895f3" } } ], "extra": [ 1, 77, 109, 252, 86, 245, 237, 244, 171, 1, 198, 227, 21, 29, 176, 17, 51, 137, 12, 189, 140, 144, 178, 138, 253, 247, 65, 132, 205, 57, 162, 180, 226, 2, 17, 0, 0, 0, 2, 151, 186, 249, 34, 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