← previous blocknext block →recent activity
Analyzing
Block #100,584,816
34 transactions · 26 stateful · 2026-08-30 22:07:18 UTC
Parallelism
88/100
Blocked
50%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,584,816 · 34 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w08w110w011w113w014w115w116w017w118w219w220w323w327w128w029w131w233w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9722304…6ed0
0x34b655…2a6f
8 touches
6 conflicts
0xc6abdbd8…415a
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xb4c703ab…f8cf
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x880b4c37…98eb
0x34b655…2a6f
4 touches
1 conflict
0xa355d425…1d82
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
6 conflicts on slot 0xd97223041d…366ed0
Audit this contract →
← previous block·next block →recent activity