Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04e7111e581413d1ef822986a10734b3492bb0e41491d5bff454f1b2df202cc3

Tx prefix hash: a10c91361d2eef8dde24a0b4d987b0b72df058cfd2533c2ec4cd5f84af21db4c
Tx public key: e269e04d1e96cd13c71ca9d0f4232b98640bf0b45c6ad79312ff40210c77e714
Timestamp: 1762593260 Timestamp [UCT]: 2025-11-08 09:14:20 Age [y:d:h:m:s]: 00:056:20:11:34
Block: 1407552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40703 RingCT/type: yes/0
Extra: 01e269e04d1e96cd13c71ca9d0f4232b98640bf0b45c6ad79312ff40210c77e714021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16441e983107462e46a212aaf06b666c459e48dc1f32974a9f551df743e69e4b 0.600000000000 1895973 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": 1407562, "vin": [ { "gen": { "height": 1407552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16441e983107462e46a212aaf06b666c459e48dc1f32974a9f551df743e69e4b" } } ], "extra": [ 1, 226, 105, 224, 77, 30, 150, 205, 19, 199, 28, 169, 208, 244, 35, 43, 152, 100, 11, 240, 180, 92, 106, 215, 147, 18, 255, 64, 33, 12, 119, 231, 20, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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