← previous blocknext block →recent activity
Analyzing
Block #99,171,475
17 transactions · 11 stateful · 2026-08-25 23:16:03 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,171,475 · 17 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
1w03w17w110w012w115w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41c56387…a8f6
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0xabfdfd0e…20bf
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xce60df54…c3e8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x41c5638713…86a8f6
Audit this contract →
← previous block·next block →recent activity