← previous blocknext block →recent activity
Analyzing
Block #104,847,489
19 transactions · 18 stateful · 2026-09-14 20:53:56 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,847,489 · 19 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
2w04w15w06w110w213w014w315w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xeb59aa82…023e
0x34b655…2a6f
4 touches
1 conflict
0xf05cf40a…dcc8
0x34b655…2a6f
4 touches
1 conflict
0x8b52b75c…8a0d
0xa6afd3…d132
4 touches
1 conflict
0x0e5eee82…7aee
0x34b655…2a6f
4 touches
1 conflict
0x25614b41…2c66
0x34b655…2a6f
4 touches
1 conflict
0x3e3f27ce…580c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
1 conflict on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity