Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f82d118f6cff04307def21b75db42701ef7e2849d5c0d9e3b63ad356818e644

Tx prefix hash: 62b813a3ffb83536ab629a43fc79f94338e8de42a5b46247782a4533a7240e4b
Tx public key: a22ef650e5af797550dfd3a1191ce328a8861c54911e3ff8bdd2b195b5dae562
Timestamp: 1726531563 Timestamp [UCT]: 2024-09-17 00:06:03 Age [y:d:h:m:s]: 00:068:18:28:03
Block: 1111701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49165 RingCT/type: yes/0
Extra: 01a22ef650e5af797550dfd3a1191ce328a8861c54911e3ff8bdd2b195b5dae56202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9a5aed49f17f268c4c1a4b6af67647307a8da5e9f62f28cc35bbe2ad1ca3cce 0.600000000000 1590754 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": 1111711, "vin": [ { "gen": { "height": 1111701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9a5aed49f17f268c4c1a4b6af67647307a8da5e9f62f28cc35bbe2ad1ca3cce" } } ], "extra": [ 1, 162, 46, 246, 80, 229, 175, 121, 117, 80, 223, 211, 161, 25, 28, 227, 40, 168, 134, 28, 84, 145, 30, 63, 248, 189, 210, 177, 149, 181, 218, 229, 98, 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