Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80708684fd08fa818acb75a6f192a49b06d92edbfb71c5527a462e49ea0e9899

Tx prefix hash: 92ed87d3afc65288e195960aaa14c10d54ab3213ce051b85c7846cdea1e4c568
Tx public key: 3ba5e800f11b2cebb0af2c61d54daa0f92e245611cecbe392c9b84e100e04c9f
Timestamp: 1740925348 Timestamp [UCT]: 2025-03-02 14:22:28 Age [y:d:h:m:s]: 00:333:18:41:57
Block: 1230569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236235 RingCT/type: yes/0
Extra: 013ba5e800f11b2cebb0af2c61d54daa0f92e245611cecbe392c9b84e100e04c9f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c5b3094dc073b8b769234244c9b775f5a40cc9335bc10c803da13638a1c9d6c 0.600000000000 1717468 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": 1230579, "vin": [ { "gen": { "height": 1230569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c5b3094dc073b8b769234244c9b775f5a40cc9335bc10c803da13638a1c9d6c" } } ], "extra": [ 1, 59, 165, 232, 0, 241, 27, 44, 235, 176, 175, 44, 97, 213, 77, 170, 15, 146, 226, 69, 97, 28, 236, 190, 57, 44, 155, 132, 225, 0, 224, 76, 159, 2, 17, 0, 0, 0, 4, 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