← previous blocknext block →recent activity
Analyzing
Block #101,502,333
13 transactions · 13 stateful · 2026-09-03 03:03:59 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,502,333 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w08w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21163f51…05d4
0x34b655…2a6f
4 touches
1 conflict
0x1ef3384e…9ab4
0x34b655…2a6f
4 touches
1 conflict
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x40fdff9c…ed8b
0x34b655…2a6f
4 touches
1 conflict
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x31576052…a592
0xd32edf…ff58
3 touches
1 conflict
0x2f17174f…68b4
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
1 conflict on slot 0x21163f51fb…0405d4
Audit this contract →
← previous block·next block →recent activity