Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 606af20cb5943c40e60776cbf194cbd89743337b3fd6ff89163abda0e7ac6085

Tx prefix hash: 003e467dfa77bea83b49f6090cf1d39ea0379d1017000ff410b031d29c54f9be
Tx public key: c4b8f636433f6fa0e8a4cb53e7ac64e0c3cd99b2e7d3a148319d2a660a6bae56
Timestamp: 1740499315 Timestamp [UCT]: 2025-02-25 16:01:55 Age [y:d:h:m:s]: 00:268:22:59:00
Block: 1227042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189978 RingCT/type: yes/0
Extra: 01c4b8f636433f6fa0e8a4cb53e7ac64e0c3cd99b2e7d3a148319d2a660a6bae560211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e92a9d85312ede1e7e5e463e18fdf882cebcaaea116cd04b926d1cf43a7fefc2 0.600000000000 1713915 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": 1227052, "vin": [ { "gen": { "height": 1227042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e92a9d85312ede1e7e5e463e18fdf882cebcaaea116cd04b926d1cf43a7fefc2" } } ], "extra": [ 1, 196, 184, 246, 54, 67, 63, 111, 160, 232, 164, 203, 83, 231, 172, 100, 224, 195, 205, 153, 178, 231, 211, 161, 72, 49, 157, 42, 102, 10, 107, 174, 86, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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