← previous blocknext block →recent activity
Analyzing
Block #100,143,147
25 transactions · 18 stateful · 2026-08-29 09:01:11 UTC
Parallelism
72/100
Blocked
61%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,143,147 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w210w312w013w117w418w419w520w621w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0acb70c1…23d5
0x34b655…2a6f
10 touches
10 conflicts
0x8fe8c690…1fd0
0xd32edf…ff58
9 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x7322fb4a…635d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0x0acb70c1b9…7323d5
Audit this contract →
← previous block·next block →recent activity