← previous blocknext block →recent activity
Analyzing
Block #102,518,219
16 transactions · 14 stateful · 2026-09-06 16:38:10 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,518,219 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w214w015w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc68ea841…b3d7
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x100812e9…12b7
0x34b655…2a6f
6 touches
3 conflicts
0x5969523e…5191
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0x65bd5b5a…58d5
0x34b655…2a6f
4 touches
1 conflict
0xa7f7a563…4504
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 0xc68ea84186…75b3d7
Audit this contract →
← previous block·next block →recent activity