← previous blocknext block →recent activity
Analyzing
Block #101,249,191
21 transactions · 18 stateful · 2026-09-02 05:50:13 UTC
Parallelism
90/100
Blocked
22%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,249,191 · 21 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
4w012w013w116w117w018w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd5a06f0…6ccd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0547420b…fc46
0x34b655…2a6f
2 touches
0 conflicts
0x132c6c23…8382
0x34b655…2a6f
2 touches
0 conflicts
0x35012b34…4843
0x34b655…2a6f
2 touches
0 conflicts
0x68c740e2…58d6
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 0xdd5a06f0a6…9f6ccd
Audit this contract →
← previous block·next block →recent activity