← previous blocknext block →recent activity
Analyzing
Block #100,591,465
22 transactions · 18 stateful · 2026-08-30 22:40:45 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,591,465 · 22 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
2w06w09w110w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0xe3ec6b34…eb5b
0x34b655…2a6f
6 touches
3 conflicts
0xbae3502c…9836
0x34b655…2a6f
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0x87aeb315…f059
0x40c49f…2af0
4 touches
1 conflict
0x36f63e4f…f319
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0x310a7246ab…012dcb
Audit this contract →
← previous block·next block →recent activity