← previous blocknext block →recent activity
Analyzing
Block #101,854,198
14 transactions · 12 stateful · 2026-09-04 08:33:57 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,854,198 · 14 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
5w08w09w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x06e89564…650d
0x10aeaf…5417
2 touches
0 conflicts
0x0dbf9688…c6cf
0x10aeaf…5417
2 touches
0 conflicts
0x1a004c59…980d
0x188d58…ea8e
2 touches
0 conflicts
0x1a004c59…980f
0x188d58…ea8e
2 touches
0 conflicts
0x3c223c30…06e6
0x1b6862…e19c
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 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity