← previous blocknext block →recent activity
Analyzing
Block #101,025,070
12 transactions · 11 stateful · 2026-09-01 11:02:25 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,025,070 · 12 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
6w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67171059…0dcd
0x34b655…2a6f
4 touches
1 conflict
0x0463db49…5d05
0x34b655…2a6f
4 touches
1 conflict
0x00f6a8a7…0e6e
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x178fe051…465a
0x34b655…2a6f
2 touches
0 conflicts
0x25191452…d2ed
0x34b655…2a6f
2 touches
0 conflicts
0x49b0842d…0a93
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 0x671710590e…010dcd
Audit this contract →
← previous block·next block →recent activity