Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5091a6dce549410c76cbb38334453e726ce9e94a641e08416d23802cc85c180

Tx prefix hash: bd40cf36780467ade6a822f88b2c324c58f88037f7ff978c924fb05a20cf00d7
Tx public key: 5d02aeb191a2480be1311d776c28e0adcb1ccc3f6706a6bbf1c57c42d14c600e
Timestamp: 1749945373 Timestamp [UCT]: 2025-06-14 23:56:13 Age [y:d:h:m:s]: 00:152:10:50:09
Block: 1305173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106720 RingCT/type: yes/0
Extra: 015d02aeb191a2480be1311d776c28e0adcb1ccc3f6706a6bbf1c57c42d14c600e0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 526b61af0df100e85bbc7aa38b22233b992b595cac873b066e8b394ee68dbcbd 0.600000000000 1792772 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": 1305183, "vin": [ { "gen": { "height": 1305173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "526b61af0df100e85bbc7aa38b22233b992b595cac873b066e8b394ee68dbcbd" } } ], "extra": [ 1, 93, 2, 174, 177, 145, 162, 72, 11, 225, 49, 29, 119, 108, 40, 224, 173, 203, 28, 204, 63, 103, 6, 166, 187, 241, 197, 124, 66, 209, 76, 96, 14, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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