← previous blocknext block →recent activity
Analyzing
Block #100,125,364
12 transactions · 12 stateful · 2026-08-29 07:31:30 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,125,364 · 12 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
7w08w09w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e28f
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e290
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e293
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e294
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e296
0x8964d7…10f8
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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity