Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68b766aa99ff37a7909c59077ded693f2ebe07557ef536f1e66b7f3e643c48dd

Tx prefix hash: e11989f81c0e9886bf18569f845aaa3d89a2d8363ee9454340f3df83de93247f
Tx public key: 87d000eb3a2da711f2eda995e414b2b9a6520e8d70c8871f79d82adcf9619d2d
Timestamp: 1625442058 Timestamp [UCT]: 2021-07-04 23:40:58 Age [y:d:h:m:s]: 03:243:23:22:38
Block: 288355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 943912 RingCT/type: yes/0
Extra: 0187d000eb3a2da711f2eda995e414b2b9a6520e8d70c8871f79d82adcf9619d2d0211000000463634f08d000000000000000000

1 output(s) for total of 68.010407636000 dcy

stealth address amount amount idx
00: ec9d1e47ccb8f1f091001352082c821f4ccd1e87c85944ca54672f470ba3559d 68.010407636000 604172 of 0

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": 288365, "vin": [ { "gen": { "height": 288355 } } ], "vout": [ { "amount": 68010407636, "target": { "key": "ec9d1e47ccb8f1f091001352082c821f4ccd1e87c85944ca54672f470ba3559d" } } ], "extra": [ 1, 135, 208, 0, 235, 58, 45, 167, 17, 242, 237, 169, 149, 228, 20, 178, 185, 166, 82, 14, 141, 112, 200, 135, 31, 121, 216, 42, 220, 249, 97, 157, 45, 2, 17, 0, 0, 0, 70, 54, 52, 240, 141, 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