← previous blocknext block →recent activity
Analyzing
Block #95,205,053
8 transactions · 6 stateful · 2026-08-12 00:31:13 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,205,053 · 8 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x320701d5…f9f4
0x34b655…2a6f
4 touches
1 conflict
0xbcf7d5d4…6901
0x34b655…2a6f
4 touches
1 conflict
0x320701d5…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x24b08f9c…e594
0x34b655…2a6f
2 touches
0 conflicts
0x2846597d…7217
0x34b655…2a6f
2 touches
0 conflicts
0x2e405dd3…f0fa
0x34b655…2a6f
2 touches
0 conflicts
0x3a5a1763…ed7c
0x34b655…2a6f
2 touches
0 conflicts
0x3a5cd535…3546
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 0x320701d57e…e5f9f4
Audit this contract →
← previous block·next block →recent activity