← previous blocknext block →recent activity
Analyzing
Block #107,817,326
28 transactions · 27 stateful · 2026-09-25 06:07:25 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,817,326 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w07w18w29w117w118w219w220w321w422w423w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
12 touches
15 conflicts
0xe98b562e…57e1
0x34b655…2a6f
8 touches
6 conflicts
0x00e21a9f…3583
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x1fb37a…a010
6 touches
3 conflicts
0xcf17589f…048c
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x1ff3c3e0…3ce5
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
15 conflicts on slot 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity