← previous blocknext block →recent activity
Analyzing
Block #100,613,675
13 transactions · 13 stateful · 2026-08-31 00:32:29 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,613,675 · 13 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
1w02w14w05w17w18w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x077cfb7e…3f26
0x34b655…2a6f
4 touches
1 conflict
0x37bdecf8…b358
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe2de1aea…8024
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0476d77b…a514
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
1 conflict on slot 0x077cfb7e8e…db3f26
Audit this contract →
← previous block·next block →recent activity