← previous blocknext block →recent activity
Analyzing
Block #105,582,967
14 transactions · 13 stateful · 2026-09-17 10:35:35 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,582,967 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w09w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee8237bd…46ad
0x34b655…2a6f
10 touches
10 conflicts
0x92f8fe7e…0cf3
0x34b655…2a6f
10 touches
10 conflicts
0x818e1296…f4d7
0x34b655…2a6f
8 touches
6 conflicts
0xca608d0c…f23b
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x581f7011…eb5b
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
10 conflicts on slot 0xee8237bda7…9e46ad
Audit this contract →
← previous block·next block →recent activity