← previous blocknext block →recent activity
Analyzing
Block #100,119,709
64 transactions · 64 stateful · 2026-08-29 07:03:02 UTC
Parallelism
94/100
Blocked
6%
Avg conflicts / tx
0.08
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,119,709 · 64 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w010w163w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9868b52…c77f
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x627738d1…db02
0x34b655…2a6f
4 touches
1 conflict
0x65389105…dfe9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
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
3 conflicts on slot 0xb9868b5233…c6c77f
Audit this contract →
← previous block·next block →recent activity