← previous blocknext block →recent activity
Analyzing
Block #101,667,002
11 transactions · 11 stateful · 2026-09-03 16:52:22 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,667,002 · 11 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
4w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd6538fb…2b3f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x110a3804…f842
0x34b655…2a6f
2 touches
0 conflicts
0x23c095cc…6318
0x34b655…2a6f
2 touches
0 conflicts
0x2d307ea7…8841
0x34b655…2a6f
2 touches
0 conflicts
0x375b6201…9c1e
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 0xdd6538fbaf…632b3f
Audit this contract →
← previous block·next block →recent activity