Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b695577348a22e34a08c9a20e8d72463e77a1bbf820492c6fa631df2b888edb3

Tx prefix hash: a2f274576458bc22e9678bc804933e62579e09a2ec90cc0bbc73201786d0c5b5
Tx public key: 106b5f6ad6e6a31a0c3e509485184e99c2cedad7dad2316f6d447cb3fa876f33
Timestamp: 1749593687 Timestamp [UCT]: 2025-06-10 22:14:47 Age [y:d:h:m:s]: 00:153:06:29:07
Block: 1302339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107220 RingCT/type: yes/0
Extra: 01106b5f6ad6e6a31a0c3e509485184e99c2cedad7dad2316f6d447cb3fa876f33021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29fa0f4fb11d25579422a927d63f7ed875e08a62d32a334952d9069736395317 0.600000000000 1789908 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": 1302349, "vin": [ { "gen": { "height": 1302339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29fa0f4fb11d25579422a927d63f7ed875e08a62d32a334952d9069736395317" } } ], "extra": [ 1, 16, 107, 95, 106, 214, 230, 163, 26, 12, 62, 80, 148, 133, 24, 78, 153, 194, 206, 218, 215, 218, 210, 49, 111, 109, 68, 124, 179, 250, 135, 111, 51, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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