← previous blocknext block →recent activity
Analyzing
Block #100,026,974
18 transactions · 17 stateful · 2026-08-28 23:16:10 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,026,974 · 18 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
10w012w113w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x639be938…49c4
0x34b655…2a6f
6 touches
3 conflicts
0x9a8482cc…8bee
0x34b655…2a6f
4 touches
1 conflict
0xb0e974c4…b84d
0x34b655…2a6f
4 touches
1 conflict
0xd2a76d80…ee44
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xffaa25f5…1528
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x7aa91b8f…d070
0x2b46c0…1669
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
3 conflicts on slot 0x639be93840…0f49c4
Audit this contract →
← previous block·next block →recent activity