← previous blocknext block →recent activity
Analyzing
Block #99,974,140
20 transactions · 18 stateful · 2026-08-28 18:50:07 UTC
Parallelism
90/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,974,140 · 20 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
1w02w16w07w111w012w113w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f63d67…5ba0
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x6742c574…dbda
0x34b655…2a6f
4 touches
1 conflict
0x7a674820…53a5
0x34b655…2a6f
4 touches
1 conflict
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xc502c499…5d7c
0xd32edf…ff58
3 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 0x60f63d6751…de5ba0
Audit this contract →
← previous block·next block →recent activity