← previous blocknext block →recent activity
Analyzing
Block #99,881,754
20 transactions · 19 stateful · 2026-08-28 11:04:34 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,881,754 · 20 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
1w02w14w05w06w110w011w114w215w016w118w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cf31a32…56e7
0x34b655…2a6f
6 touches
3 conflicts
0x3cf31547…051b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xe10ff4f0…94b7
0x99c7a7…8bf0
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x3b41d761…cd85
0x99c7a7…8bf0
4 touches
1 conflict
0x5fa6e1a0…c881
0x34b655…2a6f
4 touches
1 conflict
0x67a56c8b…f955
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
3 conflicts on slot 0x4cf31a32dd…8256e7
Audit this contract →
← previous block·next block →recent activity