Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71c52631e21237def9bee4e372c0ea147a01d0fe5a70a7d4cd870647eadb62db

Tx prefix hash: 55bccd15d5e36ea483221d7b6d021dad15aeffa725d2886fe713d0ce7c7b2fe2
Tx public key: 267229fa772bd1f30431690124301ceb180dc1a3185e221b9916f8f1dbc3684a
Timestamp: 1726518274 Timestamp [UCT]: 2024-09-16 20:24:34 Age [y:d:h:m:s]: 00:068:17:27:54
Block: 1111594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49139 RingCT/type: yes/0
Extra: 01267229fa772bd1f30431690124301ceb180dc1a3185e221b9916f8f1dbc3684a021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7d6a9b73768e382b7f816fe0f622b466fe3c9b5b485145302e8c9b1835c9261 0.600000000000 1590611 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": 1111604, "vin": [ { "gen": { "height": 1111594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7d6a9b73768e382b7f816fe0f622b466fe3c9b5b485145302e8c9b1835c9261" } } ], "extra": [ 1, 38, 114, 41, 250, 119, 43, 209, 243, 4, 49, 105, 1, 36, 48, 28, 235, 24, 13, 193, 163, 24, 94, 34, 27, 153, 22, 248, 241, 219, 195, 104, 74, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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