Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f56215759958174bf50292526e9c6191015cc25ee1f429f026cf09a0383d71a

Tx prefix hash: c33f43df698e59c92744d462aa66992e8a13687d7baf681a212d839e7d32dabc
Tx public key: a6937daf9e77e1c8063da8562f8fd784e34ce51a0055e54cc4e836f6be0b391f
Timestamp: 1752372415 Timestamp [UCT]: 2025-07-13 02:06:55 Age [y:d:h:m:s]: 00:115:13:35:23
Block: 1324291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81299 RingCT/type: yes/0
Extra: 01a6937daf9e77e1c8063da8562f8fd784e34ce51a0055e54cc4e836f6be0b391f021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee8c4c9323185c63bab735737ca18e3fb5886a99d444be3db7e45cb26c69cdda 0.600000000000 1812034 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": 1324301, "vin": [ { "gen": { "height": 1324291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee8c4c9323185c63bab735737ca18e3fb5886a99d444be3db7e45cb26c69cdda" } } ], "extra": [ 1, 166, 147, 125, 175, 158, 119, 225, 200, 6, 61, 168, 86, 47, 143, 215, 132, 227, 76, 229, 26, 0, 85, 229, 76, 196, 232, 54, 246, 190, 11, 57, 31, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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