Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c08941777b5cec4d39e0ef7e783d7569eac8345e9fe2adce5557f2487b325197

Tx prefix hash: 26700d2d62a1ca3b00a9b276f24551a25b6606909df68225271d0b67d151c23c
Tx public key: 721d69029ba507359b840dc0f341a1404c55e3c7d7e824eee63573d789e34d56
Timestamp: 1702843228 Timestamp [UCT]: 2023-12-17 20:00:28 Age [y:d:h:m:s]: 01:093:13:24:59
Block: 915312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328017 RingCT/type: yes/0
Extra: 01721d69029ba507359b840dc0f341a1404c55e3c7d7e824eee63573d789e34d56021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd06baac17a1e2013e0131a43b7d57a9ef0d9931a263bc6d3cab09fca462e86e 0.600000000000 1372706 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": 915322, "vin": [ { "gen": { "height": 915312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd06baac17a1e2013e0131a43b7d57a9ef0d9931a263bc6d3cab09fca462e86e" } } ], "extra": [ 1, 114, 29, 105, 2, 155, 165, 7, 53, 155, 132, 13, 192, 243, 65, 161, 64, 76, 85, 227, 199, 215, 232, 36, 238, 230, 53, 115, 215, 137, 227, 77, 86, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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