Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a3a5bd512a10779c20f98f5d6afb704b55fb647b6e1d5237fe0df9793208b22

Tx prefix hash: 0c6ba02d741d26e841d74f31cff34bd7c11b7c7c40a3ce46dd2ace6c87658f52
Tx public key: ca01116738e8af5f2332e79db3d41fb3b3161c38307693ea91abd025979cca43
Timestamp: 1724301545 Timestamp [UCT]: 2024-08-22 04:39:05 Age [y:d:h:m:s]: 00:233:20:22:29
Block: 1093228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166988 RingCT/type: yes/0
Extra: 01ca01116738e8af5f2332e79db3d41fb3b3161c38307693ea91abd025979cca4302110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a38d54394e7793f7e6f6ce8cba6dea4cbb6a377767e99d99c801730179b7b920 0.600000000000 1568131 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": 1093238, "vin": [ { "gen": { "height": 1093228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a38d54394e7793f7e6f6ce8cba6dea4cbb6a377767e99d99c801730179b7b920" } } ], "extra": [ 1, 202, 1, 17, 103, 56, 232, 175, 95, 35, 50, 231, 157, 179, 212, 31, 179, 179, 22, 28, 56, 48, 118, 147, 234, 145, 171, 208, 37, 151, 156, 202, 67, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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