← previous blocknext block →recent activity
Analyzing
Block #100,117,123
21 transactions · 18 stateful · 2026-08-29 06:50:01 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,117,123 · 21 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
1w04w05w17w08w19w210w311w413w414w517w119w020w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8a8db2…8a6d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x04dbb52e…fe23
0x34b655…2a6f
8 touches
6 conflicts
0xd37e070d…4ef7
0x34b655…2a6f
6 touches
3 conflicts
0xac4971f2…200b
0x34b655…2a6f
6 touches
3 conflicts
0x9d9f3717…44e7
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
10 conflicts on slot 0x5c8a8db2ad…f58a6d
Audit this contract →
← previous block·next block →recent activity