Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5a8dfc7a0f3b6eae3767e361077823cf01e28287bbf0eb1f7821c30e24dc5a6

Tx prefix hash: 556fa9605c5a41eb9b9dcf05230e9331f038348bc1c4bdf9ea507ad29ce134a4
Tx public key: 719b4aa7ca0e14381e0b9050402dd743dd73fbeec5fdd12c73d216dbd8b06471
Timestamp: 1710703847 Timestamp [UCT]: 2024-03-17 19:30:47 Age [y:d:h:m:s]: 00:285:21:33:28
Block: 980507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204636 RingCT/type: yes/0
Extra: 01719b4aa7ca0e14381e0b9050402dd743dd73fbeec5fdd12c73d216dbd8b064710211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1e423d4867d289dc1276eb685fb399fe01c5e0a7a079b5f6c0d09bd2f1c20f4 0.600000000000 1440578 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": 980517, "vin": [ { "gen": { "height": 980507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1e423d4867d289dc1276eb685fb399fe01c5e0a7a079b5f6c0d09bd2f1c20f4" } } ], "extra": [ 1, 113, 155, 74, 167, 202, 14, 20, 56, 30, 11, 144, 80, 64, 45, 215, 67, 221, 115, 251, 238, 197, 253, 209, 44, 115, 210, 22, 219, 216, 176, 100, 113, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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