← previous blocknext block →recent activity
Analyzing
Block #101,937,650
24 transactions · 20 stateful · 2026-09-04 15:35:44 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,937,650 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w010w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3d3422c…0308
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7f127ad0…2bd6
0x34b655…2a6f
2 touches
0 conflicts
0xae65f1ba…2f37
0x34b655…2a6f
2 touches
0 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xe3d3422c02…f70308
Audit this contract →
← previous block·next block →recent activity