← previous blocknext block →recent activity
Analyzing
Block #101,984,972
20 transactions · 19 stateful · 2026-09-04 19:35:40 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,984,972 · 20 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
3w05w16w28w09w110w211w313w417w518w019w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x19f8e68c…4f86
0x34b655…2a6f
4 touches
1 conflict
0x2d02f869…1f83
0x34b655…2a6f
4 touches
1 conflict
0x2e957c13…4777
0x34b655…2a6f
4 touches
1 conflict
0x474b9623…8272
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6473cfe9…e086
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity