← previous blocknext block →recent activity
Analyzing
Block #99,367,466
19 transactions · 18 stateful · 2026-08-26 15:42:22 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,367,466 · 19 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
2w04w05w16w17w09w110w212w215w317w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f65f95e…37fc
0x34b655…2a6f
8 touches
6 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 conflicts
0x29f17906…74cf
0x34b655…2a6f
6 touches
3 conflicts
0x641aed07…bcb9
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0xa71dabdf…3e38
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 0x0f65f95e2f…eb37fc
Audit this contract →
← previous block·next block →recent activity