← previous blocknext block →recent activity
Analyzing
Block #95,031,111
18 transactions · 17 stateful · 2026-08-11 09:55:29 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,031,111 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w39w410w513w014w115w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d158563…8713
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x22d93518…26d1
0x34b655…2a6f
10 touches
10 conflicts
0xff3d91c4…1a37
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x4a39a2a4…857b
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x410c23da…5793
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x3d1585630c…178713
Audit this contract →
← previous block·next block →recent activity