← previous blocknext block →recent activity
Analyzing
Block #100,740,789
22 transactions · 22 stateful · 2026-08-31 11:11:54 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,740,789 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w110w011w112w213w317w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eac7709…66c3
0x34b655…2a6f
8 touches
6 conflicts
0x7c68d10b…8386
0x34b655…2a6f
8 touches
6 conflicts
0xef048f92…572b
0x34b655…2a6f
6 touches
3 conflicts
0x42d0f569…5f4b
0x34b655…2a6f
6 touches
3 conflicts
0x506742f4…5001
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xdfbe99f3…6647
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
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
6 conflicts on slot 0x0eac770979…4766c3
Audit this contract →
← previous block·next block →recent activity