← previous blocknext block →recent activity
Analyzing
Block #105,683,901
21 transactions · 19 stateful · 2026-09-17 19:03:41 UTC
Parallelism
81/100
Blocked
16%
Avg conflicts / tx
0.19
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,683,901 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w115w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb5b61a2…b2bc
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xa0998a89…1f5a
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0xc1f5557d…51cc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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
3 conflicts on slot 0xeb5b61a29c…4fb2bc
Audit this contract →
← previous block·next block →recent activity