Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e1b4ac1cc0e18b617f20e431050ad3e859cb0abe1a79bd5e12a11598243d31f

Tx prefix hash: fa1ef5b2e08a3161b8c5ffd3fd73a6f11a7fd6d2242fe4e5deed7c4076e71e8a
Tx public key: a68423937213b79f3a1a6cd262b71ed1b840f80b0b5dc3248a3b72abfc3402d0
Timestamp: 1720817190 Timestamp [UCT]: 2024-07-12 20:46:30 Age [y:d:h:m:s]: 00:278:05:14:19
Block: 1064344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198768 RingCT/type: yes/0
Extra: 01a68423937213b79f3a1a6cd262b71ed1b840f80b0b5dc3248a3b72abfc3402d002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec5f31521c99b8d58c3fb79535c1ec98e4fe4bf7426facbdc733af6aba588978 0.600000000000 1534869 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": 1064354, "vin": [ { "gen": { "height": 1064344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec5f31521c99b8d58c3fb79535c1ec98e4fe4bf7426facbdc733af6aba588978" } } ], "extra": [ 1, 166, 132, 35, 147, 114, 19, 183, 159, 58, 26, 108, 210, 98, 183, 30, 209, 184, 64, 248, 11, 11, 93, 195, 36, 138, 59, 114, 171, 252, 52, 2, 208, 2, 17, 0, 0, 0, 4, 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