← previous blocknext block →recent activity
Analyzing
Block #99,615,004
13 transactions · 12 stateful · 2026-08-27 12:34:28 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,615,004 · 13 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
4w05w16w28w19w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf5fe80…1ffc
0x34b655…2a6f
8 touches
6 conflicts
0x4ee3389c…054a
0x34b655…2a6f
6 touches
3 conflicts
0x4d5053d1…3b7d
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x5b573018…24ff
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x75dd818d…df4c
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 0xfaf5fe80ab…a71ffc
Audit this contract →
← previous block·next block →recent activity