Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7a74e99f6efdc04c6ec16f7c414a7adecb4ed8d34b7d1fb5f0ee3a8a7e5a66b

Tx prefix hash: 09da582d71b5478e149507e0c5e292ea765e393bc9a8cf42f7712aaec2ebd74d
Tx public key: a42c9bb6102625ee15ef98a6dcb2afc64753535482293c7f328a8409d00d0d59
Timestamp: 1751285774 Timestamp [UCT]: 2025-06-30 12:16:14 Age [y:d:h:m:s]: 00:206:07:46:19
Block: 1315838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145591 RingCT/type: yes/0
Extra: 01a42c9bb6102625ee15ef98a6dcb2afc64753535482293c7f328a8409d00d0d59021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85511f59c36d5ce13eccc02e107474efdb470b48d6c208b2fd5c417c92efa05d 0.600000000000 1803495 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": 1315848, "vin": [ { "gen": { "height": 1315838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85511f59c36d5ce13eccc02e107474efdb470b48d6c208b2fd5c417c92efa05d" } } ], "extra": [ 1, 164, 44, 155, 182, 16, 38, 37, 238, 21, 239, 152, 166, 220, 178, 175, 198, 71, 83, 83, 84, 130, 41, 60, 127, 50, 138, 132, 9, 208, 13, 13, 89, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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