← previous blocknext block →recent activity
Analyzing
Block #100,612,855
16 transactions · 9 stateful · 2026-08-31 00:28:22 UTC
Parallelism
81/100
Blocked
22%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,612,855 · 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
4w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41dc0dc9…b241
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5da59c2b…d7b2
0x34b655…2a6f
4 touches
1 conflict
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
2 touches
0 conflicts
0xa18d515f…b4de
0x34b655…2a6f
2 touches
0 conflicts
0xd99d25df…ecd8
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
3 conflicts on slot 0x41dc0dc9e6…0bb241
Audit this contract →
← previous block·next block →recent activity