← previous blocknext block →recent activity
Analyzing
Block #101,937,651
16 transactions · 13 stateful · 2026-09-04 15:35:44 UTC
Parallelism
56/100
Blocked
62%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,937,651 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w18w29w310w413w214w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0505bae8…b4fb
0x34b655…2a6f
6 touches
3 conflicts
0x56c70c30…9faf
0x34b655…2a6f
6 touches
3 conflicts
0x1c803d1a…c47a
0x34b655…2a6f
6 touches
3 conflicts
0x014e90b3…470f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xfa324e43…8895
0x1b6862…e19c
4 touches
1 conflict
0x0110331c…b891
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
3 conflicts on slot 0x0505bae898…14b4fb
Audit this contract →
← previous block·next block →recent activity