← previous blocknext block →recent activity
Analyzing
Block #100,232,403
10 transactions · 10 stateful · 2026-08-29 16:30:28 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,232,403 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa387c4a5…5a66
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
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8bd4285f…7151
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