← previous blocknext block →recent activity
Analyzing
Block #101,323,536
25 transactions · 22 stateful · 2026-09-02 12:04:17 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,323,536 · 25 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
1w02w19w014w219w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
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
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xa1731f0f…1f9d
0x34b655…2a6f
4 touches
1 conflict
0xac6f24e7…c98b
0x34b655…2a6f
4 touches
1 conflict
0xcfe06a18…b5b5
0x34ae4d…3fc5
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity