← previous blocknext block →recent activity
Analyzing
Block #100,230,485
12 transactions · 11 stateful · 2026-08-29 16:20:49 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,230,485 · 12 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
3w04w05w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50832c51…5855
0x34b655…2a6f
4 touches
1 conflict
0x70e677f5…e3bd
0x34b655…2a6f
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1a0baea4…49df
0x34b655…2a6f
3 touches
1 conflict
0x5ca470e3…8a2a
0x34b655…2a6f
3 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
1 conflict on slot 0x50832c5184…e75855
Audit this contract →
← previous block·next block →recent activity