← previous blocknext block →recent activity
Analyzing
Block #101,992,298
24 transactions · 24 stateful · 2026-09-04 20:12:55 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,992,298 · 24 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
1w02w14w05w06w17w28w310w011w112w014w219w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb73a5ffd…ddee
0x34b655…2a6f
8 touches
6 conflicts
0xc0f6895c…e428
0x34b655…2a6f
8 touches
6 conflicts
0x6823c28e…594c
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xf7772b49…fc12
0x34b655…2a6f
8 touches
6 conflicts
0x6be05f69…33d9
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x5746581b…0cb1
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xb73a5ffdfa…98ddee
Audit this contract →
← previous block·next block →recent activity