← previous blocknext block →recent activity
Analyzing
Block #101,798,721
6 transactions · 5 stateful · 2026-09-04 03:54:53 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,798,721 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b4f173c…94e6
0x34b655…2a6f
4 touches
1 conflict
0xf01051a1…1ee5
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x51d0a65c…5e21
0x34b655…2a6f
3 touches
1 conflict
0x07aaf7bb…cd9f
0x34b655…2a6f
2 touches
0 conflicts
0x20e3fc83…30fa
0x34b655…2a6f
2 touches
0 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
2 touches
0 conflicts
0x4b4a604b…8695
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 0x9b4f173cee…8c94e6
Audit this contract →
← previous block·next block →recent activity