← previous blocknext block →recent activity
Analyzing
Block #101,967,116
13 transactions · 10 stateful · 2026-09-04 18:05:10 UTC
Parallelism
77/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,967,116 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w111w012w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcdcaadcf…1c9f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1444952d…1fbd
0x34b655…2a6f
2 touches
0 conflicts
0x25fd5528…ff50
0x34b655…2a6f
2 touches
0 conflicts
0x2d02f869…1f83
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x5ad5e6deb1…38e7ad
Audit this contract →
← previous block·next block →recent activity