← previous blocknext block →recent activity
Analyzing
Block #107,848,332
16 transactions · 13 stateful · 2026-09-25 08:43:29 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,848,332 · 16 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
1w04w15w26w07w18w39w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31d88d27…7617
0x34b655…2a6f
8 touches
6 conflicts
0xecff7c35…1b43
0x34b655…2a6f
8 touches
6 conflicts
0xbe512d56…38f2
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xf75c3a6b…0568
0x34b655…2a6f
4 touches
1 conflict
0x28e2f7c3…e848
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0x31d88d27c1…837617
Audit this contract →
← previous block·next block →recent activity