← previous blocknext block →recent activity
Analyzing
Block #98,445,102
16 transactions · 16 stateful · 2026-08-23 09:38:21 UTC
Parallelism
81/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,445,102 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc7b9eda…e616
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0x9816fc81…4f3c
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x256e3cc7…b84c
0x34b655…2a6f
3 touches
1 conflict
0x2ad2f4bc…1800
0x34b655…2a6f
2 touches
0 conflicts
0x31147dde…390f
0x34b655…2a6f
2 touches
0 conflicts
0x48203298…65cb
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
1 conflict on slot 0xdc7b9eda72…99e616
Audit this contract →
← previous block·next block →recent activity