← previous blocknext block →recent activity
Analyzing
Block #101,970,345
13 transactions · 11 stateful · 2026-09-04 18:21:30 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,970,345 · 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
2w03w04w111w012w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x179b31b3…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0x2aa7be4c…0f84
0x34b655…2a6f
4 touches
1 conflict
0x4113c42b…5765
0x34b655…2a6f
4 touches
1 conflict
0x4c9b66e1…e999
0x34b655…2a6f
4 touches
1 conflict
0x50d65000…ae5c
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5c7b5ec0…0764
0x34b655…2a6f
4 touches
1 conflict
0x5f749304…d1c1
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 0x179b31b3ba…e16dd2
Audit this contract →
← previous block·next block →recent activity