← previous blocknext block →recent activity
Analyzing
Block #100,619,065
17 transactions · 16 stateful · 2026-08-31 00:59:36 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,619,065 · 17 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
2w03w16w012w113w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6d40b7f…2969
0x34b655…2a6f
6 touches
3 conflicts
0xb3037bed…6b7c
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xe8f57e05…3583
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1de49243…4aa3
0x34b655…2a6f
2 touches
0 conflicts
0x58620f29…db5a
0x34b655…2a6f
2 touches
0 conflicts
0x67905f6e…02a1
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 0xa6d40b7f0d…ff2969
Audit this contract →
← previous block·next block →recent activity