← previous blocknext block →recent activity
Analyzing
Block #100,032,912
25 transactions · 16 stateful · 2026-08-28 23:46:03 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,032,912 · 25 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
1w03w117w019w120w224w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0x502b3ee1e6…227f7c
Audit this contract →
← previous block·next block →recent activity