← previous blocknext block →recent activity
Analyzing
Block #101,673,282
14 transactions · 13 stateful · 2026-09-03 17:23:58 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,673,282 · 14 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
3w012w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68596e3e…c6e6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x0b7b942e…f3f4
0x34b655…2a6f
2 touches
0 conflicts
0x2979546b…7cc3
0x34b655…2a6f
2 touches
0 conflicts
0x2ba56d60…09dc
0x34b655…2a6f
2 touches
0 conflicts
0x2d4b76b6…d903
0x34b655…2a6f
2 touches
0 conflicts
0x35269399…a92a
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 0x68596e3e63…14c6e6
Audit this contract →
← previous block·next block →recent activity