Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e734de892d565ed63362649b182605afa2b11aff5c3c1326e224d99ba97fb3e

Tx prefix hash: e6ac747c77e45d3567db2f21e00b1bc6c55b92e046a230c8eadd8ad669a91857
Tx public key: 6cb4f5e4fa45df9c48bcecc61417d0ed170efbfc7bcf7332129efd337a73784b
Timestamp: 1764327028 Timestamp [UCT]: 2025-11-28 10:50:28 Age [y:d:h:m:s]: 00:025:13:16:01
Block: 1421919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18282 RingCT/type: yes/0
Extra: 016cb4f5e4fa45df9c48bcecc61417d0ed170efbfc7bcf7332129efd337a73784b02110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bedc0dbc16939b9d4b0c1d259ccc3ff5b075fc8b72ae9bf5e89615838d4bb0e0 0.600000000000 1910482 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": 1421929, "vin": [ { "gen": { "height": 1421919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bedc0dbc16939b9d4b0c1d259ccc3ff5b075fc8b72ae9bf5e89615838d4bb0e0" } } ], "extra": [ 1, 108, 180, 245, 228, 250, 69, 223, 156, 72, 188, 236, 198, 20, 23, 208, 237, 23, 14, 251, 252, 123, 207, 115, 50, 18, 158, 253, 51, 122, 115, 120, 75, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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