← previous blocknext block →recent activity
Analyzing
Block #101,248,445
13 transactions · 11 stateful · 2026-09-02 05:46:28 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,248,445 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w08w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2c4da1c…0e41
0x34b655…2a6f
4 touches
1 conflict
0xe2c4da1c…0e42
0x34b655…2a6f
4 touches
1 conflict
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0x2eb75a72…0654
0x34b655…2a6f
4 touches
1 conflict
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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 0xe2c4da1cbb…c60e41
Audit this contract →
← previous block·next block →recent activity