← previous blocknext block →recent activity
Analyzing
Block #98,481,278
18 transactions · 15 stateful · 2026-08-23 12:40:43 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,481,278 · 18 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
8w09w111w213w315w016w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x58fb4cd2…ef29
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x30908823…a62d
0x34b655…2a6f
4 touches
1 conflict
0x92e8d8dd…3752
0x34b655…2a6f
4 touches
1 conflict
0x5102bdd1…c53c
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity