← previous blocknext block →recent activity
Analyzing
Block #101,988,008
15 transactions · 12 stateful · 2026-09-04 19:51:07 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,988,008 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9816fc81…4f3c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x7db61668…8067
0x34b655…2a6f
6 touches
3 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
6 touches
3 conflicts
0xe77c721b…7588
0x34b655…2a6f
6 touches
3 conflicts
0x3bad8f8a…6d0b
0x34b655…2a6f
4 touches
1 conflict
0x1db5837f…1264
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 0x9816fc8156…184f3c
Audit this contract →
← previous block·next block →recent activity