← previous blocknext block →recent activity
Analyzing
Block #99,262,903
12 transactions · 11 stateful · 2026-08-26 06:56:08 UTC
Parallelism
75/100
Blocked
18%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,262,903 · 12 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
2w03w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x46c55070…3a42
0x34b655…2a6f
4 touches
1 conflict
0xa91691e2…e135
0x34b655…2a6f
4 touches
1 conflict
0xab3ad3dc…2a56
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xcb0d828c…ef32
0x34b655…2a6f
4 touches
1 conflict
0xd64bf3c4…45af
0x34b655…2a6f
4 touches
1 conflict
0x65678b70…10c8
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 0x6f132c01d5…7dcdcd
Audit this contract →
← previous block·next block →recent activity