← previous blocknext block →recent activity
Analyzing
Block #100,613,431
15 transactions · 13 stateful · 2026-08-31 00:31:15 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,613,431 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w06w19w210w311w112w414w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf37f31a…a7fc
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0xfc24540b…6463
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0x49a384b0…634c
0x34b655…2a6f
6 touches
3 conflicts
0xe2de1aea…8024
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 0xdf37f31ad2…b7a7fc
Audit this contract →
← previous block·next block →recent activity