← previous blocknext block →recent activity
Analyzing
Block #101,970,890
16 transactions · 13 stateful · 2026-09-04 18:24:15 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,970,890 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w114w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b024b98…8f37
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x5c7b5ec0…0764
0x34b655…2a6f
6 touches
3 conflicts
0xedbc2bb3…6b83
0x34b655…2a6f
6 touches
3 conflicts
0xf18803af…e7a5
0x34b655…2a6f
6 touches
3 conflicts
0x26c599c1…706c
0x34b655…2a6f
6 touches
3 conflicts
0x79ec4509…1f61
0x34b655…2a6f
4 touches
1 conflict
0x8b02c6c4…4011
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 0x4b024b9810…978f37
Audit this contract →
← previous block·next block →recent activity