← previous blocknext block →recent activity
Analyzing
Block #101,670,514
17 transactions · 16 stateful · 2026-09-03 17:10:03 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,670,514 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x460ccb65…17a8
0x34b655…2a6f
4 touches
1 conflict
0x56833c19…9f66
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0259de4d…a4dd
0x34b655…2a6f
2 touches
0 conflicts
0x074dd821…1b9c
0x34b655…2a6f
2 touches
0 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
2 touches
0 conflicts
0x3f25409b…f92b
0x34b655…2a6f
2 touches
0 conflicts
0x5a780dcf…0d26
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 0x460ccb65fb…1a17a8
Audit this contract →
← previous block·next block →recent activity