← previous blocknext block →recent activity
Analyzing
Block #101,492,410
16 transactions · 14 stateful · 2026-09-03 02:14:04 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,492,410 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w010w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8a8db2…8a6d
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x04dbb52e…fe23
0x34b655…2a6f
4 touches
1 conflict
0x50a77b58…db53
0xd32edf…ff58
3 touches
1 conflict
0x729c91b8…9538
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…953a
0x188d58…ea8e
2 touches
0 conflicts
0xd1bd1ac3…3496
0x188d58…ea8e
2 touches
0 conflicts
0xd1bd1ac3…3497
0x188d58…ea8e
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
1 conflict on slot 0x5c8a8db2ad…f58a6d
Audit this contract →
← previous block·next block →recent activity