← previous blocknext block →recent activity
Analyzing
Block #105,636,118
19 transactions · 18 stateful · 2026-09-17 15:03:10 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,636,118 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w513w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3dfc072c…ed4e
0x34b655…2a6f
12 touches
15 conflicts
0xc5847c4d…a65c
0x34b655…2a6f
12 touches
15 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
8 touches
6 conflicts
0x6771eae2…7014
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x8968fc32…20e3
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x3dfc072c58…97ed4e
Audit this contract →
← previous block·next block →recent activity