← previous blocknext block →recent activity
Analyzing
Block #100,232,399
18 transactions · 16 stateful · 2026-08-29 16:30:27 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,232,399 · 18 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
1w08w111w013w014w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa387c4a5…5a66
0x8964d7…10f8
4 touches
1 conflict
0xa387c4a5…5a5f
0x8964d7…10f8
4 touches
1 conflict
0xa387c4a5…5a60
0x8964d7…10f8
4 touches
1 conflict
0xa387c4a5…5a63
0x8964d7…10f8
4 touches
1 conflict
0xa387c4a5…5a64
0x8964d7…10f8
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xa387c4a598…525a66
Audit this contract →
← previous block·next block →recent activity