← previous blocknext block →recent activity
Analyzing
Block #102,329,144
28 transactions · 27 stateful · 2026-09-06 00:40:04 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,329,144 · 28 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
2w03w16w010w011w113w215w121w323w224w326w127w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a69a8a3…40ad
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x7c2869d6…1203
0x34b655…2a6f
4 touches
1 conflict
0x91a74d74…548c
0x34b655…2a6f
4 touches
1 conflict
0x9cf9008a…d826
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
6 conflicts on slot 0x6a69a8a30a…ab40ad
Audit this contract →
← previous block·next block →recent activity