← previous blocknext block →recent activity
Analyzing
Block #107,802,869
21 transactions · 18 stateful · 2026-09-25 04:54:40 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,802,869 · 21 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
1w03w16w07w08w110w211w113w314w415w416w218w019w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bd71786…2d83
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa8d1cb8c…dd1c
0x34b655…2a6f
4 touches
1 conflict
0xaa3cf307…30e8
0x34b655…2a6f
4 touches
1 conflict
0xab52a7ec…2bcc
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
6 conflicts on slot 0x2bd7178683…a02d83
Audit this contract →
← previous block·next block →recent activity