← previous blocknext block →recent activity
Analyzing
Block #107,815,679
19 transactions · 19 stateful · 2026-09-25 05:59:08 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,815,679 · 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
1w02w18w09w110w211w312w313w414w516w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
12 touches
15 conflicts
0x73b0c753…42e2
0x34b655…2a6f
12 touches
15 conflicts
0x232b0b19…d946
0x34b655…2a6f
10 touches
10 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4611acd1…c536
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 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity