← previous blocknext block →recent activity
Analyzing
Block #99,478,161
17 transactions · 15 stateful · 2026-08-27 00:59:44 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,478,161 · 17 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
2w03w14w05w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x945d1dbe…e1d7
0xc8689a…ee79
4 touches
1 conflict
0x4387ba94…e195
0x34b655…2a6f
4 touches
1 conflict
0x076b9edf…e35c
0x34b655…2a6f
2 touches
0 conflicts
0x16d77246…bac5
0x34b655…2a6f
2 touches
0 conflicts
0x359866c7…de7b
0x34b655…2a6f
2 touches
0 conflicts
0x37c0660b…e0bf
0x34b655…2a6f
2 touches
0 conflicts
0x48d4896a…d0c6
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity