Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b26a5fc474894fbf5a2d6065b3df9e8d36117d4243bf6053c6aa669cf21bbdcd

Tx prefix hash: bfe8c089c69712c90aaf4a730e16e41e41325cbdb2f8e614608d8fe0114f898d
Tx public key: f9b8705cc0b45adc5368c36233d2afcc7d2e810d762b383784d9a611f2a02879
Timestamp: 1741327464 Timestamp [UCT]: 2025-03-07 06:04:24 Age [y:d:h:m:s]: 00:259:03:35:19
Block: 1233911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182949 RingCT/type: yes/0
Extra: 01f9b8705cc0b45adc5368c36233d2afcc7d2e810d762b383784d9a611f2a028790211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a6572f364215cb1aa852be0976219f2826275369237eac9a160d6f0260a5845 0.600000000000 1720836 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": 1233921, "vin": [ { "gen": { "height": 1233911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a6572f364215cb1aa852be0976219f2826275369237eac9a160d6f0260a5845" } } ], "extra": [ 1, 249, 184, 112, 92, 192, 180, 90, 220, 83, 104, 195, 98, 51, 210, 175, 204, 125, 46, 129, 13, 118, 43, 56, 55, 132, 217, 166, 17, 242, 160, 40, 121, 2, 17, 0, 0, 0, 5, 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