Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae9f8213dd6c862046258f7698d0814d102ea4ffd48733f0f2f5b1c25071bf26

Tx prefix hash: c0518ce504023a11a364878ac8dc7df2e2ba7f09de5081f183b40e8a55e3e0fb
Tx public key: 6792f2cc45d879376611deb02d0fe1501e4b0712e6cb9502d403e880f09df79e
Timestamp: 1761018708 Timestamp [UCT]: 2025-10-21 03:51:48 Age [y:d:h:m:s]: 00:102:13:15:02
Block: 1394518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73232 RingCT/type: yes/0
Extra: 016792f2cc45d879376611deb02d0fe1501e4b0712e6cb9502d403e880f09df79e02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f12beab8ea79a2eab91cb82527732777c7d25e8d5805c749abed5aa9a0dd254a 0.600000000000 1882789 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": 1394528, "vin": [ { "gen": { "height": 1394518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f12beab8ea79a2eab91cb82527732777c7d25e8d5805c749abed5aa9a0dd254a" } } ], "extra": [ 1, 103, 146, 242, 204, 69, 216, 121, 55, 102, 17, 222, 176, 45, 15, 225, 80, 30, 75, 7, 18, 230, 203, 149, 2, 212, 3, 232, 128, 240, 157, 247, 158, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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