← previous blocknext block →recent activity
Analyzing
Block #95,196,327
19 transactions · 19 stateful · 2026-08-11 23:47:20 UTC
Parallelism
89/100
Blocked
16%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,196,327 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w013w014w116w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x335ef294…03f3
0x34b655…2a6f
4 touches
1 conflict
0x294e28fe…7589
0x40c49f…2af0
4 touches
1 conflict
0x3d9eb674…b3fb
0x754704…b603
4 touches
1 conflict
0x94ce6be0…d3ad
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0b10a52b…ac19
0xd18b7e…414b
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x737acb78…fce8
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: Perpl
1 conflict on slot 0x335ef29485…8103f3
Audit this contract →
← previous block·next block →recent activity