Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a17fd557b26fc3b867df5972b2723306667b67700f4c62f9f3a5388ac4b816e

Tx prefix hash: 7b542382f5c2cda8728d0212e499cd7a5e43425f064bc6afaea5587e58e8501e
Tx public key: a119a6dd5335aeff21e90171a0c06a4a8b34f3085a04eddfddebd8b9c6cce1d3
Timestamp: 1721471612 Timestamp [UCT]: 2024-07-20 10:33:32 Age [y:d:h:m:s]: 00:299:18:43:53
Block: 1069756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214181 RingCT/type: yes/0
Extra: 01a119a6dd5335aeff21e90171a0c06a4a8b34f3085a04eddfddebd8b9c6cce1d3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aca8321e23d65c05ab4d96ba966303d770e7c91fce11805ff2d40b0804352e42 0.600000000000 1541313 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": 1069766, "vin": [ { "gen": { "height": 1069756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aca8321e23d65c05ab4d96ba966303d770e7c91fce11805ff2d40b0804352e42" } } ], "extra": [ 1, 161, 25, 166, 221, 83, 53, 174, 255, 33, 233, 1, 113, 160, 192, 106, 74, 139, 52, 243, 8, 90, 4, 237, 223, 221, 235, 216, 185, 198, 204, 225, 211, 2, 17, 0, 0, 0, 4, 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