← previous blocknext block →recent activity
Analyzing
Block #101,992,827
31 transactions · 11 stateful · 2026-09-04 20:15:36 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.16
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,992,827 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
22w023w127w129w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb73a5ffd…ddee
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xc0f6895c…e428
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1dc71894…1884
0x34b655…2a6f
4 touches
1 conflict
0x04d4f30d…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5746581b…0cb1
0x34b655…2a6f
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 0xb73a5ffdfa…98ddee
Audit this contract →
← previous block·next block →recent activity