← previous blocknext block →recent activity
Analyzing
Block #100,892,147
13 transactions · 10 stateful · 2026-08-31 23:53:41 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,892,147 · 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
1w02w13w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x23082fb8…cbfe
0x754704…b603
4 touches
1 conflict
0x2e618acf…234f
0x754704…b603
4 touches
1 conflict
0xd0fa1733…0b67
0x754704…b603
4 touches
1 conflict
0x5336a768…986f
0x99c7a7…8bf0
4 touches
1 conflict
0x9cbb3d8d…2dd6
0x99c7a7…8bf0
4 touches
1 conflict
0x60dc7b78…d1d5
0x34b655…2a6f
2 touches
0 conflicts
0x68c740e2…58d6
0x34b655…2a6f
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity