Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6381d8de6caa7700d848121f0f54df820820ad5c3e65fea4c35297114e7631a

Tx prefix hash: 5e874eb4f3d7717c2ed8efbc99a4ec6deadccbd1c17c3079a2375364e42fb31a
Tx public key: 172721531ef1e0920d8c3a7cf38a217766a7e26c9443636f6e2257e52ccde517
Timestamp: 1728359280 Timestamp [UCT]: 2024-10-08 03:48:00 Age [y:d:h:m:s]: 00:092:22:18:16
Block: 1126854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66430 RingCT/type: yes/0
Extra: 01172721531ef1e0920d8c3a7cf38a217766a7e26c9443636f6e2257e52ccde517021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16e1f69a45e8810fb902ac798b4ae92985e7186d487ac1ee2317f64df5aea9f8 0.600000000000 1609651 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": 1126864, "vin": [ { "gen": { "height": 1126854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16e1f69a45e8810fb902ac798b4ae92985e7186d487ac1ee2317f64df5aea9f8" } } ], "extra": [ 1, 23, 39, 33, 83, 30, 241, 224, 146, 13, 140, 58, 124, 243, 138, 33, 119, 102, 167, 226, 108, 148, 67, 99, 111, 110, 34, 87, 229, 44, 205, 229, 23, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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