← previous blocknext block →recent activity
Analyzing
Block #101,924,544
17 transactions · 13 stateful · 2026-09-04 14:29:09 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,924,544 · 17 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
1w03w07w18w29w313w014w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08db2444…22b2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf6532bc5…89f2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc95f91db…a901
0x34b655…2a6f
4 touches
1 conflict
0xe3acd35d…06ab
0x34b655…2a6f
4 touches
1 conflict
0xedbdf454…0ae3
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 0x08db24449d…5f22b2
Audit this contract →
← previous block·next block →recent activity