← previous blocknext block →recent activity
Analyzing
Block #105,542,350
18 transactions · 14 stateful · 2026-09-17 07:11:09 UTC
Parallelism
61/100
Blocked
57%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,542,350 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w08w211w312w413w514w616w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x451a771d…2a72
0x34b655…2a6f
14 touches
21 conflicts
0x18978822…2623
0x34b655…2a6f
10 touches
10 conflicts
0xb5f5f775…010b
0x34b655…2a6f
6 touches
3 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0x70f537e8…399b
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x03f7a75e…f2a8
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0x451a771d14…6f2a72
Audit this contract →
← previous block·next block →recent activity