← previous blocknext block →recent activity
Analyzing
Block #101,674,887
38 transactions · 38 stateful · 2026-09-03 17:32:03 UTC
Parallelism
92/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,674,887 · 38 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
4w05w06w19w137w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64b7d292…67c9
0x34b655…2a6f
4 touches
1 conflict
0xa6214594…6a6a
0x34b655…2a6f
4 touches
1 conflict
0xac970b4d…fb51
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd2facdba…7a7e
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x2be34971…27ba
0x34b655…2a6f
4 touches
1 conflict
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
1 conflict on slot 0x64b7d292e1…f267c9
Audit this contract →
← previous block·next block →recent activity