← previous blocknext block →recent activity
Analyzing
Block #100,616,611
21 transactions · 18 stateful · 2026-08-31 00:47:15 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,616,611 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w09w110w212w216w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfce7dfe…5053
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb8
0x1b6862…e19c
4 touches
1 conflict
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x252edae0…e9be
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
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
3 conflicts on slot 0xdfce7dfe53…c75053
Audit this contract →
← previous block·next block →recent activity