← previous blocknext block →recent activity
Analyzing
Block #99,871,514
15 transactions · 14 stateful · 2026-08-28 10:12:59 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,871,514 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w09w110w211w312w414w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fc68901…9dcc
0x34b655…2a6f
8 touches
6 conflicts
0x0d03bddb…6658
0x34b655…2a6f
8 touches
6 conflicts
0xebdcd2dd…fa70
0x34b655…2a6f
4 touches
1 conflict
0xf15273a1…2c52
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x9bf019ed…6b13
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 0x8fc6890137…369dcc
Audit this contract →
← previous block·next block →recent activity