Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c05aef93faeed55e63cc7b778a91b6cd7e7dab625fd3616f5a01328a2f26c928

Tx prefix hash: 780da42ae03f55d9d2cd7c05e5f0d3a1fa90919e79dc5d738f1a8913c0a8466b
Tx public key: 335067d3f47ad6d226169f3d38c04de9d6d1164e35831e3cfd6134a31557a25a
Timestamp: 1685388713 Timestamp [UCT]: 2023-05-29 19:31:53 Age [y:d:h:m:s]: 01:180:03:12:22
Block: 770866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390131 RingCT/type: yes/0
Extra: 01335067d3f47ad6d226169f3d38c04de9d6d1164e35831e3cfd6134a31557a25a02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.713172573000 dcy

stealth address amount amount idx
00: d0f3543772cac632ca46dbed1b5c2a2ec81a4871a8d0f53f08c4f2eb9929b211 1.713172573000 1220199 of 0

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": 770876, "vin": [ { "gen": { "height": 770866 } } ], "vout": [ { "amount": 1713172573, "target": { "key": "d0f3543772cac632ca46dbed1b5c2a2ec81a4871a8d0f53f08c4f2eb9929b211" } } ], "extra": [ 1, 51, 80, 103, 211, 244, 122, 214, 210, 38, 22, 159, 61, 56, 192, 77, 233, 214, 209, 22, 78, 53, 131, 30, 60, 253, 97, 52, 163, 21, 87, 162, 90, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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