Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b530667aa4fa6f15fe0619dd160952da92f62ce9cc35c229a4f33980a8509633

Tx prefix hash: 5dcfb461cb8cfc807856d89c166878bc114ca12789814655c040201d74325fd8
Tx public key: c32fb067420a779e529b354ada996e15304b4b0d48dc644c63a5d7b429f7e2d4
Timestamp: 1693027399 Timestamp [UCT]: 2023-08-26 05:23:19 Age [y:d:h:m:s]: 01:236:05:11:03
Block: 834104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429983 RingCT/type: yes/0
Extra: 01c32fb067420a779e529b354ada996e15304b4b0d48dc644c63a5d7b429f7e2d402110000000375e3f0e9000000000000000000

1 output(s) for total of 1.057468099000 dcy

stealth address amount amount idx
00: 8ea7f749ecaea05d7548ff771961ad6bf2fe8d698fb4cd69c1a77f2bcc294945 1.057468099000 1286590 of 0

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": 834114, "vin": [ { "gen": { "height": 834104 } } ], "vout": [ { "amount": 1057468099, "target": { "key": "8ea7f749ecaea05d7548ff771961ad6bf2fe8d698fb4cd69c1a77f2bcc294945" } } ], "extra": [ 1, 195, 47, 176, 103, 66, 10, 119, 158, 82, 155, 53, 74, 218, 153, 110, 21, 48, 75, 75, 13, 72, 220, 100, 76, 99, 165, 215, 180, 41, 247, 226, 212, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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