Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65224b989280f44a759c9664983d90d07a4eff6388f97b06b0b040aeacb37ae6

Tx prefix hash: 46d4879a44b1fb80ad85b64f8fc15abe0fc2303517aec994f7650c5d1f85a4de
Tx public key: c3609adbd8b7f1418f2ca20e4d181012029bed535cfd7616c4aa1591df884505
Timestamp: 1745386446 Timestamp [UCT]: 2025-04-23 05:34:06 Age [y:d:h:m:s]: 00:212:11:22:09
Block: 1267501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149578 RingCT/type: yes/0
Extra: 01c3609adbd8b7f1418f2ca20e4d181012029bed535cfd7616c4aa1591df8845050211000000126c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9621f8dc9d86891d2f0080b723b1072e19dc108dbb41d6555d05673f0b269bc 0.600000000000 1754730 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": 1267511, "vin": [ { "gen": { "height": 1267501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9621f8dc9d86891d2f0080b723b1072e19dc108dbb41d6555d05673f0b269bc" } } ], "extra": [ 1, 195, 96, 154, 219, 216, 183, 241, 65, 143, 44, 162, 14, 77, 24, 16, 18, 2, 155, 237, 83, 92, 253, 118, 22, 196, 170, 21, 145, 223, 136, 69, 5, 2, 17, 0, 0, 0, 18, 108, 152, 170, 61, 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