← previous blocknext block →recent activity
Analyzing
Block #101,087,575
13 transactions · 13 stateful · 2026-09-01 16:17:12 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,087,575 · 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
2w04w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedee7e09…6888
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x0bcc353d…5302
0x34b655…2a6f
2 touches
0 conflicts
0x6326afd0…fd59
0x34b655…2a6f
2 touches
0 conflicts
0x796f27bf…e5c9
0x34b655…2a6f
2 touches
0 conflicts
0xa5a233a4…fd0f
0x34b655…2a6f
2 touches
0 conflicts
0xbf3feb6b…9378
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 0xedee7e090f…056888
Audit this contract →
← previous block·next block →recent activity