← previous blocknext block →recent activity
Analyzing
Block #102,549,048
16 transactions · 15 stateful · 2026-09-06 19:14:33 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,549,048 · 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
1w02w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x37c0660b…e0bf
0x34b655…2a6f
2 touches
0 conflicts
0x3c0e49c9…7833
0x34b655…2a6f
2 touches
0 conflicts
0x75f928fc…0465
0x34b655…2a6f
2 touches
0 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
2 touches
0 conflicts
0x94e7f277…471b
0x34b655…2a6f
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 0x6ca15e14f4…917be8
Audit this contract →
← previous block·next block →recent activity