← previous blocknext block →recent activity
Analyzing
Block #98,480,123
9 transactions · 9 stateful · 2026-08-23 12:34:55 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,480,123 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x272e5bd6…252d
0x34b655…2a6f
4 touches
1 conflict
0x2f0c960e…1d38
0x34b655…2a6f
4 touches
1 conflict
0x8248048f…8724
0x34b655…2a6f
4 touches
1 conflict
0xd1cdeb5a…1da1
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9289
0x2b46c0…1669
2 touches
0 conflicts
0x3ba7edbb…80e6
0x2b46c0…1669
2 touches
0 conflicts
0x53e50026…6d8c
0x2b46c0…1669
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
1 conflict on slot 0x00f245ce7e…641e10
Audit this contract →
← previous block·next block →recent activity