Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 389052ead2f99d5bcff08d3794d4fefd4d8c1a17cfda75de17414249f84151dd

Tx prefix hash: f5c0aa03e3287f33c4a02d5f5a9820a471ea01fd27388c5a2e0617f4357c2a0c
Tx public key: 85ee25423080a52818e099ab1c6a8bda8e037b9e7fd0b6d57618dfc3563d8eb1
Timestamp: 1709452938 Timestamp [UCT]: 2024-03-03 08:02:18 Age [y:d:h:m:s]: 01:257:22:29:26
Block: 970124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443075 RingCT/type: yes/0
Extra: 0185ee25423080a52818e099ab1c6a8bda8e037b9e7fd0b6d57618dfc3563d8eb10211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24a6758380ebd42f4aab8b25022fa9c8ffb5cea0be60f667b799fbeca835b54a 0.600000000000 1429973 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": 970134, "vin": [ { "gen": { "height": 970124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24a6758380ebd42f4aab8b25022fa9c8ffb5cea0be60f667b799fbeca835b54a" } } ], "extra": [ 1, 133, 238, 37, 66, 48, 128, 165, 40, 24, 224, 153, 171, 28, 106, 139, 218, 142, 3, 123, 158, 127, 208, 182, 213, 118, 24, 223, 195, 86, 61, 142, 177, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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