← previous blocknext block →recent activity
Analyzing
Block #101,681,525
18 transactions · 17 stateful · 2026-09-03 18:05:26 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,681,525 · 18 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
2w03w14w05w16w28w010w112w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf6c5f75…cfcd
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x32e1d03e…68a7
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x5812d190…2f1e
0x34b655…2a6f
4 touches
1 conflict
0x582cac9c…2571
0x34b655…2a6f
4 touches
1 conflict
0x5f42d9c4…9b28
0x34b655…2a6f
4 touches
1 conflict
0x6823c28e…594c
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 0xbf6c5f7571…48cfcd
Audit this contract →
← previous block·next block →recent activity