← previous blocknext block →recent activity
Analyzing
Block #105,366,840
15 transactions · 13 stateful · 2026-09-16 16:27:47 UTC
Parallelism
87/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,366,840 · 15 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
1w02w14w05w06w17w08w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c7c1a4b…5751
0x34b655…2a6f
4 touches
1 conflict
0xc7d734c2…b3f8
0x34b655…2a6f
4 touches
1 conflict
0xd4f6a526…ad10
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xfcd7574f…a3a2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
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 0x6c7c1a4b7d…d35751
Audit this contract →
← previous block·next block →recent activity