← previous blocknext block →recent activity
Analyzing
Block #105,636,006
24 transactions · 23 stateful · 2026-09-17 15:02:36 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,636,006 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w19w010w211w312w413w314w515w616w719w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x213b816c…a5e0
0x34b655…2a6f
12 touches
15 conflicts
0x90a021f0…f922
0x34b655…2a6f
10 touches
10 conflicts
0x166cd7f7…2b93
0x34b655…2a6f
10 touches
10 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf346808d…6ad4
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 0x213b816cc7…d4a5e0
Audit this contract →
← previous block·next block →recent activity