← previous blocknext block →recent activity
Analyzing
Block #95,182,739
17 transactions · 16 stateful · 2026-08-11 22:38:59 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,182,739 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w09w110w211w312w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ffa3328…ce11
0xe52b14…7230
10 touches
10 conflicts
0xe1902c61…65ad
0xe52b14…7230
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0x15b0eca0…3c35
0xe52b14…7230
8 touches
10 conflicts
0xa6e37efb…afc0
0xe52b14…7230
8 touches
6 conflicts
0xa6e37efb…afc2
0xe52b14…7230
8 touches
6 conflicts
0x58733c38…f2cd
0xe52b14…7230
4 touches
1 conflict
0x693b762e…1fcd
0xe52b14…7230
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0xe52b1424…bb7230
10 conflicts on slot 0x8ffa332881…c9ce11
Audit this contract →
← previous block·next block →recent activity