← previous blocknext block →recent activity
Analyzing
Block #100,787,163
25 transactions · 24 stateful · 2026-08-31 15:05:20 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,787,163 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w18w111w112w213w314w416w217w318w020w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xd2dfd9bc…3eec
0x34b655…2a6f
6 touches
3 conflicts
0x1d9154e7…8821
0x34b655…2a6f
4 touches
1 conflict
0x1e6a1604…0ef0
0x34b655…2a6f
4 touches
1 conflict
0x4a99ba46…452f
0x34b655…2a6f
4 touches
1 conflict
0x5dda0222…bf9c
0x34b655…2a6f
4 touches
1 conflict
0x71628448…ce07
0x34b655…2a6f
4 touches
1 conflict
0x76622fb2…4f08
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity