← previous blocknext block →recent activity
Analyzing
Block #107,823,039
19 transactions · 19 stateful · 2026-09-25 06:36:11 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,823,039 · 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
1w02w14w05w18w09w110w211w312w413w214w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x66fc0764…05fd
0x34b655…2a6f
10 touches
10 conflicts
0xbf496a61…9dcc
0x34b655…2a6f
10 touches
10 conflicts
0x64275949…d698
0x34b655…2a6f
10 touches
10 conflicts
0x09331726…a1bf
0x34b655…2a6f
8 touches
6 conflicts
0x3f5831e5…02b2
0x34b655…2a6f
8 touches
6 conflicts
0x5d63456d…6681
0x34b655…2a6f
8 touches
6 conflicts
0x342ab04a…e2fa
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity