Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b11fdb25f8811f57e5be791bcb32e89fcabc89b070cc6a0ef4a08405577f2cf3

Tx prefix hash: b54416014b6f9a6eff4e2ca5a9cf98a2ed996965299cb22fee8bcdb6fd96b8c0
Tx public key: a26f7bcdade980e1f2986af25aab1cb76ac69c9bd9bac3492a9c8d33bf8ca392
Timestamp: 1708807647 Timestamp [UCT]: 2024-02-24 20:47:27 Age [y:d:h:m:s]: 01:040:15:49:45
Block: 964770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290077 RingCT/type: yes/0
Extra: 01a26f7bcdade980e1f2986af25aab1cb76ac69c9bd9bac3492a9c8d33bf8ca39202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75a7e40a7ead513b09b22bc592a7cddb8bff9e24c5fab4e07082522e031496e2 0.600000000000 1424513 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": 964780, "vin": [ { "gen": { "height": 964770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75a7e40a7ead513b09b22bc592a7cddb8bff9e24c5fab4e07082522e031496e2" } } ], "extra": [ 1, 162, 111, 123, 205, 173, 233, 128, 225, 242, 152, 106, 242, 90, 171, 28, 183, 106, 198, 156, 155, 217, 186, 195, 73, 42, 156, 141, 51, 191, 140, 163, 146, 2, 17, 0, 0, 0, 2, 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