← previous blocknext block →recent activity
Analyzing
Block #101,300,281
28 transactions · 24 stateful · 2026-09-02 10:07:16 UTC
Parallelism
82/100
Blocked
46%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,300,281 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w26w38w09w110w111w212w314w020w222w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0x06e40499…165e
0x34ae4d…3fc5
4 touches
1 conflict
0x48ed1159…abe9
0x34ae4d…3fc5
4 touches
1 conflict
0xa605468c…1bfc
0x34ae4d…3fc5
4 touches
1 conflict
0x152f8e3d…3da0
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity