← previous blocknext block →recent activity
Analyzing
Block #95,074,636
22 transactions · 21 stateful · 2026-08-11 13:35:12 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,074,636 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w18w09w110w211w012w115w116w217w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xeae24c…0be0
6 touches
3 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xaea2f389…0305
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
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: 0xeae24c72…e30be0
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity