Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0440c2c04375a40a2a3fe401da3be66c3d35d49504f182b4d24d7a33557a7c4f

Tx prefix hash: 1f26b62cf6550a80a6f743c73a890fbbbed696ef438b587d79a1ac70a5779dad
Tx public key: 8e769f116c653f51dc2e5096c5ebe8c7af93b1b3d9731ddc63d7a8dc5743776e
Timestamp: 1725179842 Timestamp [UCT]: 2024-09-01 08:37:22 Age [y:d:h:m:s]: 00:084:08:54:52
Block: 1100500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60332 RingCT/type: yes/0
Extra: 018e769f116c653f51dc2e5096c5ebe8c7af93b1b3d9731ddc63d7a8dc5743776e021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7adc977b78b8f94888422cd1d194234a910793ce4689864f74b59db46c57f502 0.600000000000 1576479 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": 1100510, "vin": [ { "gen": { "height": 1100500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7adc977b78b8f94888422cd1d194234a910793ce4689864f74b59db46c57f502" } } ], "extra": [ 1, 142, 118, 159, 17, 108, 101, 63, 81, 220, 46, 80, 150, 197, 235, 232, 199, 175, 147, 177, 179, 217, 115, 29, 220, 99, 215, 168, 220, 87, 67, 119, 110, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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