← previous blocknext block →recent activity
Analyzing
Block #107,848,476
24 transactions · 15 stateful · 2026-09-25 08:44:12 UTC
Parallelism
92/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,848,476 · 24 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w18w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4646dd5…0b8e
0x34b655…2a6f
4 touches
1 conflict
0xc484e851…6a7b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xc22d9d7a…331e
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x8d175439…fb79
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0x3e1e8e54…9c83
0x2a68ba…90c5
2 touches
0 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
1 conflict on slot 0xc4646dd579…610b8e
Audit this contract →
← previous block·next block →recent activity