← previous blocknext block →recent activity
Analyzing
Block #107,815,430
26 transactions · 20 stateful · 2026-09-25 05:57:53 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,815,430 · 26 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
2w03w16w07w18w211w012w113w114w223w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc6f8e10…1c35
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa2434b71…1910
0x34b655…2a6f
4 touches
1 conflict
0xaa654491…2ca4
0x34b655…2a6f
4 touches
1 conflict
0xb64b9585…6270
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
3 conflicts on slot 0xcc6f8e1070…6b1c35
Audit this contract →
← previous block·next block →recent activity