Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be6060d750cd1787924b4f64089d79b1ae3ea3c0ae0714138b48542362026c5

Tx prefix hash: ee96788101e2b8ce1dcdd52fd9c141319310a987d32b35c1f2b1ecf2b89eb47d
Tx public key: e17f826e46d6a84720ba26a2068f8f08736db6aabe374ecd3c75dc79949b0bdc
Timestamp: 1706975342 Timestamp [UCT]: 2024-02-03 15:49:02 Age [y:d:h:m:s]: 01:051:23:02:02
Block: 949559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298181 RingCT/type: yes/0
Extra: 01e17f826e46d6a84720ba26a2068f8f08736db6aabe374ecd3c75dc79949b0bdc02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 946a0d12ea64d0ee2bda877046e09b4e0cdea3036334ef343b2c85a63d81363d 0.600000000000 1408089 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": 949569, "vin": [ { "gen": { "height": 949559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "946a0d12ea64d0ee2bda877046e09b4e0cdea3036334ef343b2c85a63d81363d" } } ], "extra": [ 1, 225, 127, 130, 110, 70, 214, 168, 71, 32, 186, 38, 162, 6, 143, 143, 8, 115, 109, 182, 170, 190, 55, 78, 205, 60, 117, 220, 121, 148, 155, 11, 220, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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