← previous blocknext block →recent activity
Analyzing
Block #104,148,749
13 transactions · 12 stateful · 2026-09-12 09:51:17 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,148,749 · 13 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
2w04w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e7e0120…7bb9
0x34b655…2a6f
4 touches
1 conflict
0x705a9a1a…db08
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x087f8f14…c9a1
0x34b655…2a6f
2 touches
0 conflicts
0x3270d9f8…099a
0x34b655…2a6f
2 touches
0 conflicts
0x3e1329b8…deca
0x34b655…2a6f
2 touches
0 conflicts
0x488a6c81…f676
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 0x5e7e01206e…6c7bb9
Audit this contract →
← previous block·next block →recent activity