← previous blocknext block →recent activity
Analyzing
Block #101,669,305
11 transactions · 10 stateful · 2026-09-03 17:03:58 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,669,305 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64b7d292…67c9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x01315072…0e2d
0x34b655…2a6f
2 touches
0 conflicts
0x01b0fa8e…173c
0x34b655…2a6f
2 touches
0 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x10bdd1d1…23db
0x34b655…2a6f
2 touches
0 conflicts
0x29a58269…011a
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 0x64b7d292e1…f267c9
Audit this contract →
← previous block·next block →recent activity