← previous blocknext block →recent activity
Analyzing
Block #100,144,514
14 transactions · 13 stateful · 2026-08-29 09:08:03 UTC
Parallelism
50/100
Blocked
46%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,144,514 · 14 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
1w04w05w16w28w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ed1f9d0…fc7f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x0c76a5b5…8b5b
0x34b655…2a6f
8 touches
6 conflicts
0xa35a015f…ab3b
0x34b655…2a6f
6 touches
3 conflicts
0x612a8656…e330
0x34b655…2a6f
6 touches
3 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
4 touches
1 conflict
0x6719a767…9d62
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
10 conflicts on slot 0x5ed1f9d00b…62fc7f
Audit this contract →
← previous block·next block →recent activity