← previous blocknext block →recent activity
Analyzing
Block #100,022,845
14 transactions · 13 stateful · 2026-08-28 22:55:23 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,022,845 · 14 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
2w04w05w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x24c5620c…7ac5
0x34b655…2a6f
2 touches
0 conflicts
0x2d65ee7d…0d06
0x34b655…2a6f
2 touches
0 conflicts
0x34f96536…244a
0x34b655…2a6f
2 touches
0 conflicts
0x4eefdd44…5d3d
0x34b655…2a6f
2 touches
0 conflicts
0x51cfbcbc…fa29
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity