← previous blocknext block →recent activity
Analyzing
Block #101,937,643
18 transactions · 9 stateful · 2026-09-04 15:35:42 UTC
Parallelism
89/100
Blocked
22%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,937,643 · 18 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
13w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676052f0…a5f6
0x34b655…2a6f
4 touches
1 conflict
0x8a02d049…f481
0x34b655…2a6f
4 touches
1 conflict
0x46356904…5ead
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
2 touches
0 conflicts
0x014e90b3…470f
0x34b655…2a6f
2 touches
0 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
2 touches
0 conflicts
0x0513d655…45ce
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 0x676052f056…30a5f6
Audit this contract →
← previous block·next block →recent activity