← previous blocknext block →recent activity
Analyzing
Block #104,033,632
15 transactions · 15 stateful · 2026-09-12 00:05:22 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,033,632 · 15 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
1w02w15w28w09w112w314w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf30c163…0fb6
0x34b655…2a6f
8 touches
6 conflicts
0xe3f37e64…31eb
0x34b655…2a6f
4 touches
1 conflict
0x6be58ee5…4502
0x34b655…2a6f
4 touches
1 conflict
0x6e5d9b07…ceac
0x34b655…2a6f
4 touches
1 conflict
0x87248345…d544
0x34b655…2a6f
4 touches
1 conflict
0xac6f24e7…c98b
0x34b655…2a6f
4 touches
1 conflict
0xbf68b5d2…0eba
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0xaf30c16357…c70fb6
Audit this contract →
← previous block·next block →recent activity