← previous blocknext block →recent activity
Analyzing
Block #99,812,048
24 transactions · 24 stateful · 2026-08-28 05:12:31 UTC
Parallelism
92/100
Blocked
13%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,812,048 · 24 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
6w08w09w111w012w119w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe1170c6f…1d73
0x34b655…2a6f
4 touches
1 conflict
0xff3ed4c7…82e9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
2 touches
0 conflicts
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 0x2fdfa03271…56139c
Audit this contract →
← previous block·next block →recent activity