← previous blocknext block →recent activity
Analyzing
Block #100,868,757
38 transactions · 35 stateful · 2026-08-31 21:56:02 UTC
Parallelism
95/100
Blocked
6%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,868,757 · 38 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
1w02w03w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x451e482b…7e7d
0x34b655…2a6f
4 touches
1 conflict
0x04dead37…96fd
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x03da5c00…b353
0x34b655…2a6f
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x11e1e2a4…54fb
0x34b655…2a6f
2 touches
0 conflicts
0x450fb5b7…9760
0x34b655…2a6f
2 touches
0 conflicts
0x47e2a668…be99
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 0x451e482b59…427e7d
Audit this contract →
← previous block·next block →recent activity