Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae540934dc078b6c55810abab4c2290d4128c06f3f4b97251c7e1094c6648cb6

Tx prefix hash: 922e637e418891a80dd237cdafd74b77ffbf2ae46fb0b49bce9f0d2d83a53994
Tx public key: 66c3b7628b6ee8f37164ef822604f75c19892087d2004c8456c8b9324b9d5910
Timestamp: 1703110650 Timestamp [UCT]: 2023-12-20 22:17:30 Age [y:d:h:m:s]: 01:136:08:34:22
Block: 917555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358578 RingCT/type: yes/0
Extra: 0166c3b7628b6ee8f37164ef822604f75c19892087d2004c8456c8b9324b9d5910021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c936ba0ac3bf4b5df367fb72cf7842df91b6d0a82aaa237a91700c98238d8d7d 0.600000000000 1375137 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": 917565, "vin": [ { "gen": { "height": 917555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c936ba0ac3bf4b5df367fb72cf7842df91b6d0a82aaa237a91700c98238d8d7d" } } ], "extra": [ 1, 102, 195, 183, 98, 139, 110, 232, 243, 113, 100, 239, 130, 38, 4, 247, 92, 25, 137, 32, 135, 210, 0, 76, 132, 86, 200, 185, 50, 75, 157, 89, 16, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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