Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e52f8ab16e7fd12fc4b7da275ae2c08a3e2fe9200719d88971ec8f1a52d18fe9

Tx prefix hash: 1512d9bf5dbebd91ad930f5713160b1052d59f756a138e545646e971c37a1750
Tx public key: 6311bf2730094a54888fd95f13c50563d2f7f4b7b06eda643fc2cbdbab360f3e
Timestamp: 1709032180 Timestamp [UCT]: 2024-02-27 11:09:40 Age [y:d:h:m:s]: 01:038:14:25:39
Block: 966632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288594 RingCT/type: yes/0
Extra: 016311bf2730094a54888fd95f13c50563d2f7f4b7b06eda643fc2cbdbab360f3e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 857674f0e4071927218186f989d66b5a1c1605fff18f06f0fa588092e12781ce 0.600000000000 1426399 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": 966642, "vin": [ { "gen": { "height": 966632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "857674f0e4071927218186f989d66b5a1c1605fff18f06f0fa588092e12781ce" } } ], "extra": [ 1, 99, 17, 191, 39, 48, 9, 74, 84, 136, 143, 217, 95, 19, 197, 5, 99, 210, 247, 244, 183, 176, 110, 218, 100, 63, 194, 203, 219, 171, 54, 15, 62, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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