← previous blocknext block →recent activity
Analyzing
Block #107,815,419
21 transactions · 18 stateful · 2026-09-25 05:57:49 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,815,419 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w08w19w110w211w313w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0f6f4f2…dffa
0x34b655…2a6f
6 touches
3 conflicts
0x00e21a9f…3583
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xa77cfc4e…1c54
0x34b655…2a6f
6 touches
3 conflicts
0xa23b9051…392f
0x34b655…2a6f
6 touches
3 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x3a663e9a…a9cd
0x508254…98bd
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
3 conflicts on slot 0xd0f6f4f225…4cdffa
Audit this contract →
← previous block·next block →recent activity