← previous blocknext block →recent activity
Analyzing
Block #101,322,937
19 transactions · 18 stateful · 2026-09-02 12:01:16 UTC
Parallelism
89/100
Blocked
28%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,322,937 · 19 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
4w05w18w012w114w115w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb975a6c…bff4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x44330547…f55e
0x851145…3f07
4 touches
1 conflict
0x4940258b…0b39
0x851145…3f07
4 touches
1 conflict
0x60d98bf5…fa99
0x851145…3f07
4 touches
1 conflict
0x7de57974…f5ba
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 0xbb975a6cb4…7fbff4
Audit this contract →
← previous block·next block →recent activity