← previous blocknext block →recent activity
Analyzing
Block #101,152,332
19 transactions · 17 stateful · 2026-09-01 21:42:57 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,152,332 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w19w214w316w017w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0dd7e169…6f12
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4b67947a…c3bd
0x34b655…2a6f
4 touches
1 conflict
0xa91691e2…e135
0x34b655…2a6f
3 touches
1 conflict
0xac206e47…ef7d
0x34b655…2a6f
2 touches
0 conflicts
0xb2e9ab60…6e48
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity