← previous blocknext block →recent activity
Analyzing
Block #100,619,567
12 transactions · 12 stateful · 2026-08-31 01:02:07 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,619,567 · 12 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w26w37w48w510w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfce7dfe…5053
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd265ee7d…a4f7
0x34b655…2a6f
6 touches
3 conflicts
0x4f225a2e…ed90
0x34b655…2a6f
4 touches
1 conflict
0x83ec1322…c4ad
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
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: Perpl
15 conflicts on slot 0xdfce7dfe53…c75053
Audit this contract →
← previous block·next block →recent activity