← previous blocknext block →recent activity
Analyzing
Block #101,969,594
13 transactions · 13 stateful · 2026-09-04 18:17:43 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,969,594 · 13 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
2w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e81c352…1b26
0x34b655…2a6f
4 touches
1 conflict
0x91b13e91…855d
0x34b655…2a6f
4 touches
1 conflict
0xc87e767e…4bba
0x34b655…2a6f
4 touches
1 conflict
0xe4d866fb…6efa
0x34b655…2a6f
4 touches
1 conflict
0x0b9d0dba…872d
0x34b655…2a6f
2 touches
0 conflicts
0x15dd196f…8973
0x34b655…2a6f
2 touches
0 conflicts
0x1d56e4c4…2bed
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity