Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8710fd41bca7c711d1eb3fe6a92f96825c81c8a5591bd5806f8e7eb04d17c3c7

Tx prefix hash: 1605ffb95512827de1824285e91e5b667184e1674d4b538f6a0661c3365ecde8
Tx public key: ec46e38bdc65613ce552e3eec007246c947360b7a8fcffcab1ce68ab5e7a167e
Timestamp: 1730400434 Timestamp [UCT]: 2024-10-31 18:47:14 Age [y:d:h:m:s]: 00:342:10:07:09
Block: 1143701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242247 RingCT/type: yes/0
Extra: 01ec46e38bdc65613ce552e3eec007246c947360b7a8fcffcab1ce68ab5e7a167e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90dfd9d1499733a1b6a32836e2f92e7941a4aadd52a0703f8e7d6f2eba3433e1 0.600000000000 1627662 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": 1143711, "vin": [ { "gen": { "height": 1143701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90dfd9d1499733a1b6a32836e2f92e7941a4aadd52a0703f8e7d6f2eba3433e1" } } ], "extra": [ 1, 236, 70, 227, 139, 220, 101, 97, 60, 229, 82, 227, 238, 192, 7, 36, 108, 148, 115, 96, 183, 168, 252, 255, 202, 177, 206, 104, 171, 94, 122, 22, 126, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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