← previous blocknext block →recent activity
Analyzing
Block #100,631,268
17 transactions · 13 stateful · 2026-08-31 02:00:59 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,631,268 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w011w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa5fc0e5…ff18
0x34b655…2a6f
6 touches
3 conflicts
0x6940ae48…0c29
0x34b655…2a6f
6 touches
3 conflicts
0xe09e365c…b22d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7f104800…0476
0x34b655…2a6f
4 touches
1 conflict
0xa11b60f7…8e8b
0x34b655…2a6f
4 touches
1 conflict
0xa4c5f5b1…82f8
0x34b655…2a6f
4 touches
1 conflict
0xa7f7a563…4504
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xfa5fc0e52f…4fff18
Audit this contract →
← previous block·next block →recent activity