← previous blocknext block →recent activity
Analyzing
Block #105,462,109
8 transactions · 8 stateful · 2026-09-17 00:27:21 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,462,109 · 8 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
1w02w05w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0bb33e3f…7072
0x34b655…2a6f
2 touches
0 conflicts
0x3a1711ab…1ee8
0x34b655…2a6f
2 touches
0 conflicts
0x59d2df30…aff2
0x34b655…2a6f
2 touches
0 conflicts
0x67c1f465…38b3
0x34b655…2a6f
2 touches
0 conflicts
0x6c5b8c3c…1b41
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity