← previous blocknext block →recent activity
Analyzing
Block #104,198,557
32 transactions · 25 stateful · 2026-09-12 14:04:07 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,198,557 · 32 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
1w02w13w04w05w06w17w213w014w118w019w120w021w122w224w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01a720cc…00d5
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xb73bc4d0…c656
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x14a5bae7…65e4
0x34b655…2a6f
5 touches
3 conflicts
0x7aa5d2c4…d6ef
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 0x01a720cc5a…5e00d5
Audit this contract →
← previous block·next block →recent activity