← previous blocknext block →recent activity
Analyzing
Block #100,140,358
22 transactions · 20 stateful · 2026-08-29 08:47:08 UTC
Parallelism
59/100
Blocked
60%
Avg conflicts / tx
1.45
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,140,358 · 22 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w16w29w210w311w413w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc67c406…e655
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa11b60f7…8e8b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x4a39a2a4…857b
0x34b655…2a6f
8 touches
6 conflicts
0xa169711f…c7f3
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
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 0xfc67c4066d…67e655
Audit this contract →
← previous block·next block →recent activity