← previous blocknext block →recent activity
Analyzing
Block #108,684,682
16 transactions · 14 stateful · 2026-09-28 06:53:23 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,684,682 · 16 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
1w02w03w110w111w012w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9c5
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c8
0x508254…98bd
4 touches
1 conflict
0x0e0c66fe…796f
0x1e2721…7805
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x431fa96d…6ac0
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0x1e2721…7805
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x9ae4aa46…597f
0x754704…b603
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: 0x508254c8…4a98bd
1 conflict on slot 0x3a663e9a3a…2fa9c5
Audit this contract →
← previous block·next block →recent activity