← previous blocknext block →recent activity
Analyzing
Block #100,141,320
18 transactions · 16 stateful · 2026-08-29 08:51:59 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,141,320 · 18 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
3w09w010w111w213w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7a6768d…8840
0x34b655…2a6f
8 touches
6 conflicts
0x1e737223…2278
0x34b655…2a6f
6 touches
3 conflicts
0xfd13df66…0029
0x34b655…2a6f
6 touches
3 conflicts
0x1d0f9e2e…9742
0x34b655…2a6f
4 touches
1 conflict
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xc406772a…2313
0x34b655…2a6f
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 0xa7a6768d9b…828840
Audit this contract →
← previous block·next block →recent activity