← previous blocknext block →recent activity
Analyzing
Block #101,023,596
19 transactions · 15 stateful · 2026-09-01 10:55:00 UTC
Parallelism
89/100
Blocked
20%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,023,596 · 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
5w06w19w010w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5c0d2f…7301
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0x9f394e15…65c1
0x34b655…2a6f
4 touches
1 conflict
0xb0e974c4…b84d
0x34b655…2a6f
4 touches
1 conflict
0xd7908b5f…56b9
0x34b655…2a6f
4 touches
1 conflict
0xdfce7dfe…5053
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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 0x1a5c0d2fa1…937301
Audit this contract →
← previous block·next block →recent activity