← previous blocknext block →recent activity
Analyzing
Block #100,724,387
9 transactions · 8 stateful · 2026-08-31 09:49:24 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,724,387 · 9 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x823a7ba9…34c9
0x34b655…2a6f
4 touches
1 conflict
0xdc8d7edd…8a03
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x191e0467…70e5
0x34b655…2a6f
2 touches
0 conflicts
0x54c6fb44…369a
0x34b655…2a6f
2 touches
0 conflicts
0x6a2a5f12…e5dc
0x34b655…2a6f
2 touches
0 conflicts
0x9240d9ba…2115
0x34b655…2a6f
2 touches
0 conflicts
0xa5ab7b8a…c97b
0x34b655…2a6f
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 0x823a7ba90e…d834c9
Audit this contract →
← previous block·next block →recent activity