← previous blocknext block →recent activity
Analyzing
Block #101,065,436
17 transactions · 17 stateful · 2026-09-01 14:25:33 UTC
Parallelism
88/100
Blocked
12%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,065,436 · 17 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
4w010w013w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c926c97…0436
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xab3ad3dc…2a56
0x34b655…2a6f
4 touches
1 conflict
0xb5924647…4cf1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x400e87c1…4db7
0x34b655…2a6f
2 touches
0 conflicts
0x6bce5317…a995
0x34b655…2a6f
2 touches
0 conflicts
0x7cdf3968…b396
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 0x5c926c9765…ce0436
Audit this contract →
← previous block·next block →recent activity