← previous blocknext block →recent activity
Analyzing
Block #100,434,128
17 transactions · 16 stateful · 2026-08-30 09:29:09 UTC
Parallelism
65/100
Blocked
31%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,434,128 · 17 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
5w06w17w29w310w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4db508b8…b746
0x34b655…2a6f
12 touches
15 conflicts
0xb3aa2022…9e09
0x34b655…2a6f
8 touches
6 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x9711d76f…8e5c
0x34b655…2a6f
6 touches
3 conflicts
0x4d6cf1f2…26f8
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
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
15 conflicts on slot 0x4db508b8cf…f8b746
Audit this contract →
← previous block·next block →recent activity