← previous blocknext block →recent activity
Analyzing
Block #100,578,176
16 transactions · 14 stateful · 2026-08-30 21:33:54 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,578,176 · 16 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
4w06w18w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bb07d5e…582e
0x34b655…2a6f
4 touches
1 conflict
0x820d7282…6c34
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x01477139…97b0
0x34b655…2a6f
2 touches
0 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x6ac4a9ce…5f63
0x34b655…2a6f
2 touches
0 conflicts
0xd8834cf3…0004
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 0x3bb07d5e78…08582e
Audit this contract →
← previous block·next block →recent activity