← previous blocknext block →recent activity
Analyzing
Block #105,634,062
18 transactions · 17 stateful · 2026-09-17 14:52:49 UTC
Parallelism
89/100
Blocked
12%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,634,062 · 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
1w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b54bf38…d5b6
0x34b655…2a6f
4 touches
1 conflict
0x6f32a04c…0e17
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x88e92ec7…696d
0x34b655…2a6f
4 touches
1 conflict
0x09020e03…31e5
0x34b655…2a6f
2 touches
0 conflicts
0x0ac8a40d…f11f
0x34b655…2a6f
2 touches
0 conflicts
0x20660957…910d
0x34b655…2a6f
2 touches
0 conflicts
0x232df012…c608
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 0x4b54bf38d5…b4d5b6
Audit this contract →
← previous block·next block →recent activity