← previous blocknext block →recent activity
Analyzing
Block #100,160,380
8 transactions · 8 stateful · 2026-08-29 10:27:56 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,160,380 · 8 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
4w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x52e0faa1…d718
0x34b655…2a6f
4 touches
1 conflict
0x0da71bf6…4d35
0x34b655…2a6f
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x7a66a2b7…8e38
0x8964d7…10f8
4 touches
1 conflict
0x7a66a2b7…8e39
0x8964d7…10f8
4 touches
1 conflict
0x7a66a2b7…8e3c
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 0x4bf59d22eb…3300de
Audit this contract →
← previous block·next block →recent activity