← previous blocknext block →recent activity
Analyzing
Block #107,849,124
28 transactions · 26 stateful · 2026-09-25 08:47:28 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,849,124 · 28 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
2w03w05w06w18w19w210w314w216w317w018w119w220w321w422w523w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9516933a…4130
0x34b655…2a6f
8 touches
6 conflicts
0x54e6d2a8…ec22
0x34b655…2a6f
8 touches
6 conflicts
0xa489b3e9…865c
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x49b0842d…0a93
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
6 conflicts on slot 0x9516933a0d…d24130
Audit this contract →
← previous block·next block →recent activity