← previous blocknext block →recent activity
Analyzing
Block #99,170,239
13 transactions · 13 stateful · 2026-08-25 23:09:50 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,170,239 · 13 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
1w02w03w04w16w17w08w19w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ab4ac1a…c2ec
0x34b655…2a6f
4 touches
1 conflict
0x1b3f5f5c…64c2
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x4ec687a7…7f1e
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
1 conflict on slot 0x1ab4ac1a1a…98c2ec
Audit this contract →
← previous block·next block →recent activity