← previous blocknext block →recent activity
Analyzing
Block #101,673,765
15 transactions · 13 stateful · 2026-09-03 17:26:24 UTC
Parallelism
60/100
Blocked
46%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,673,765 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w311w012w113w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32e1d03e…68a7
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x898a08aa…c855
0x34b655…2a6f
8 touches
6 conflicts
0xfa805f95…72a4
0x34b655…2a6f
6 touches
3 conflicts
0x1c0b6641…28c3
0x34b655…2a6f
6 touches
3 conflicts
0x477cb4f5…11b4
0x34b655…2a6f
6 touches
3 conflicts
0x620d97c3…a92b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x32e1d03e9d…d168a7
Audit this contract →
← previous block·next block →recent activity