← previous blocknext block →recent activity
Analyzing
Block #107,278,097
24 transactions · 23 stateful · 2026-09-23 08:51:14 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,278,097 · 24 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
1w02w03w14w05w29w111w314w416w118w119w420w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bd4088b…62b9
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5dd8a950…d089
0x34b655…2a6f
6 touches
3 conflicts
0x06ec654f…48b7
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x52fa0ad8…be77
0x34b655…2a6f
4 touches
1 conflict
0x6c26d635…1bbf
0x34b655…2a6f
4 touches
1 conflict
0x6cad301f…15b7
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 0x6bd4088b4e…5a62b9
Audit this contract →
← previous block·next block →recent activity