← previous blocknext block →recent activity
Analyzing
Block #95,746,656
13 transactions · 13 stateful · 2026-08-13 22:10:01 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,746,656 · 13 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
5w06w18w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x517157d5…68df
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xdba3b90b…02bd
0x34b655…2a6f
4 touches
1 conflict
0xf18c12c4…3e7d
0x34b655…2a6f
4 touches
1 conflict
0xa41d2d7c…ccf6
0x065c9d…c394
3 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
2 touches
0 conflicts
0x7f63a266…68c0
0x34b655…2a6f
2 touches
0 conflicts
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 0x517157d51c…c468df
Audit this contract →
← previous block·next block →recent activity