← previous blocknext block →recent activity
Analyzing
Block #99,854,073
13 transactions · 12 stateful · 2026-08-28 08:44:57 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,854,073 · 13 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
2w03w16w08w09w110w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe108b282…58b3
0x34b655…2a6f
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0xf1917e9e…2db9
0x8964d7…10f8
4 touches
1 conflict
0xf1917e9e…2dba
0x8964d7…10f8
4 touches
1 conflict
0xf1917e9e…2dbd
0x8964d7…10f8
4 touches
1 conflict
0xf1917e9e…2dbe
0x8964d7…10f8
4 touches
1 conflict
0x482471ad…122f
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 0xe108b28272…6558b3
Audit this contract →
← previous block·next block →recent activity