← previous blocknext block →recent activity
Analyzing
Block #100,618,219
18 transactions · 18 stateful · 2026-08-31 00:55:20 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,618,219 · 18 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
1w05w16w27w38w09w413w514w616w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4edbf2d2…36bc
0x34b655…2a6f
6 touches
3 conflicts
0x1408a100…f721
0x34b655…2a6f
4 touches
1 conflict
0x279ddfdc…78fb
0x34b655…2a6f
4 touches
1 conflict
0x279ddfdc…78fc
0x34b655…2a6f
4 touches
1 conflict
0x2e1f5171…ad2d
0x34b655…2a6f
4 touches
1 conflict
0x35b0198e…3e0d
0x34b655…2a6f
4 touches
1 conflict
0x51c8b4fa…003e
0x34b655…2a6f
4 touches
1 conflict
0x5e8a4db9…a764
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
3 conflicts on slot 0x4edbf2d22c…f636bc
Audit this contract →
← previous block·next block →recent activity