← previous blocknext block →recent activity
Analyzing
Block #100,618,358
18 transactions · 17 stateful · 2026-08-31 00:56:02 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
1.44
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,618,358 · 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
1w02w15w26w37w48w59w012w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8db32935…81a7
0x34b655…2a6f
14 touches
21 conflicts
0x1d17ba18…e2f1
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x758a0dd5…0f46
0x34b655…2a6f
6 touches
3 conflicts
0xeecc325e…0637
0x34b655…2a6f
4 touches
1 conflict
0x05cdc9b4…d6d3
0x34b655…2a6f
4 touches
1 conflict
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
21 conflicts on slot 0x8db3293548…c981a7
Audit this contract →
← previous block·next block →recent activity