Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b893782688c64e54fe61cfdea2ef0d6e9db6ae0d6a7a95f718f473423bb91e9

Tx prefix hash: a9dddf32698fde6fe7ff4f65d326ec2947a0501e84896344789af6bac15e7b7c
Tx public key: 765d0eee817e35ae5f0cf9d76c3cd957432703c7082de784a31af625a3da55aa
Timestamp: 1722124878 Timestamp [UCT]: 2024-07-28 00:01:18 Age [y:d:h:m:s]: 00:258:21:46:59
Block: 1075172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184950 RingCT/type: yes/0
Extra: 01765d0eee817e35ae5f0cf9d76c3cd957432703c7082de784a31af625a3da55aa02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77abb44b129494b3f7e096e9020b3ecbfefee1355ad13549f1230902036e783f 0.600000000000 1547695 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": 1075182, "vin": [ { "gen": { "height": 1075172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77abb44b129494b3f7e096e9020b3ecbfefee1355ad13549f1230902036e783f" } } ], "extra": [ 1, 118, 93, 14, 238, 129, 126, 53, 174, 95, 12, 249, 215, 108, 60, 217, 87, 67, 39, 3, 199, 8, 45, 231, 132, 163, 26, 246, 37, 163, 218, 85, 170, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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