← previous blocknext block →recent activity
Analyzing
Block #107,823,024
30 transactions · 28 stateful · 2026-09-25 06:36:06 UTC
Parallelism
73/100
Blocked
39%
Avg conflicts / tx
1.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,823,024 · 30 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
1w02w15w09w112w013w114w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
14 touches
21 conflicts
0xbf496a61…9dcc
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x64275949…d698
0x34b655…2a6f
8 touches
6 conflicts
0x15a642a7…3b84
0x34b655…2a6f
8 touches
6 conflicts
0x3f5831e5…02b2
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x09331726…a1bf
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
21 conflicts on slot 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity