Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c77829aae55828c5eaecce9c14e2ed9a432764d04772c6e59b26f3e11b245df0

Tx prefix hash: bc508275ea8c92760727f903d1d875b92e254321933f4cdd8602240662eab74b
Tx public key: 6c0d7686bed195d79761aff85dc6e26928157d555ed9b601531a9aa5a3c70109
Timestamp: 1730614495 Timestamp [UCT]: 2024-11-03 06:14:55 Age [y:d:h:m:s]: 00:078:14:32:33
Block: 1145469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56199 RingCT/type: yes/0
Extra: 016c0d7686bed195d79761aff85dc6e26928157d555ed9b601531a9aa5a3c701090211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37e5cc0f607173db494627ddc5c375750a4019b00e90c4b70b0ce6406abcffb0 0.600000000000 1629906 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": 1145479, "vin": [ { "gen": { "height": 1145469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37e5cc0f607173db494627ddc5c375750a4019b00e90c4b70b0ce6406abcffb0" } } ], "extra": [ 1, 108, 13, 118, 134, 190, 209, 149, 215, 151, 97, 175, 248, 93, 198, 226, 105, 40, 21, 125, 85, 94, 217, 182, 1, 83, 26, 154, 165, 163, 199, 1, 9, 2, 17, 0, 0, 0, 6, 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