← previous blocknext block →recent activity
Analyzing
Block #99,851,742
11 transactions · 11 stateful · 2026-08-28 08:33:13 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,851,742 · 11 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
1w02w14w05w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61fe66ad…cb68
0x34b655…2a6f
6 touches
3 conflicts
0x65ff54af…aa01
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0x8a346c59…9694
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x61fe66ad98…9bcb68
Audit this contract →
← previous block·next block →recent activity